MCP server: `reply-to-ticket` ignores the "Draft Reply" permission. Can a draft reply tool be added?

Hi team,

First, thanks for shipping the MCP server. I connected an AI agent to Fluent Support this week and the read tools work very well.

I ran into one thing I'd like to raise, plus a feature request.

Setup

• Fluent Support MCP Server 2.4.0 (as reported by initialize)
• A dedicated agent user for the AI, connected with an application password
• Agent permissions: View Dashboard, Manage Own / Unassigned / Others Tickets, Draft Reply
• Not granted: Approve Draft Reply

What I expected
Because the agent has "Draft Reply" but not "Approve Draft Reply", I expected a reply created through the MCP tool fluent-support-reply-to-ticket to be saved as a draft that waits for approval, the same way it works in the web interface.

What happens
The reply is sent to the customer immediately.

On a test ticket, the tool returned "Reply added to ticket #… and assigned to you". The response was stored with type: response and source: mcp, the ticket moved from new to active, the activity log shows response_added_by_agent … via mcp, and the customer email went out. No draft was created and nothing waited for approval.

Why it matters
With AI agents, a human approval step before anything reaches a customer is the whole point. Today the only safe setup is to hide the reply tool from the agent entirely, which means a human has to copy the text and send it by hand. The approval gate already exists in Fluent Support. It just isn't applied on the MCP route.

My questions

1. Is it intended that fluent-support-reply-to-ticket bypasses the "Draft Reply" permission, or is that a bug?
2. Could the tool respect that permission, so that an agent with "Draft Reply" and without "Approve Draft Reply" creates a draft instead of sending?
3. Alternatively, could you add a separate tool, for example fluent-support-create-draft-reply, that only ever creates a draft for a human to approve in the dashboard? A matching read tool that lists pending drafts would make it complete.

Option 3 would be my preference. An explicit "draft only" tool is easy to allow on its own, and it makes it impossible for a misconfigured agent to send by accident.

Steps to reproduce

1. Create an agent with "Draft Reply" and without "Approve Draft Reply".
2. Connect to the MCP endpoint as that agent.
3. Call fluent-support-reply-to-ticket with a ticket_id and content on a test ticket.
4. The reply is sent and emailed to the customer, not held as a draft.

Happy to test a build or share more detail if useful.

Thanks,
Hans