AI agents use draft_reply_tool to create or update resources in IMAP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your IMAP MCP Server environment.
Drafting an email reply creates new, reversible content (Write category). It does not execute external commands, delete data, or move money. Severity is medium because a misdrafted reply could send unintended messages, but drafts are typically reviewed before sending, limiting immediate harm. The empty description prevents higher confidence.
From the tool's definition Tool name is 'draft_reply_tool' which drafts email replies. The sibling tool 'draft_meeting_reply_tool' and the server's purpose of 'manage email' confirm this creates new email content. Empty description lowers confidence slightly.
Documented attack patterns abuse exactly the kind of access draft_reply_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and IMAP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for draft_reply_tool:
{
"version": "1",
"default": "deny",
"tools": {
"draft_reply_tool": {
"limits": [
{
"counter": "draft_reply_tool_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}draft_reply_tool stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
draft_reply_tool. It is categorised as a Write tool in the IMAP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the IMAP MCP Server MCP server in PolicyLayer and add a rule for draft_reply_tool: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches IMAP MCP Server. Nothing to install.
draft_reply_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the draft_reply_tool rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for draft_reply_tool. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
draft_reply_tool is provided by the IMAP MCP Server MCP server (non-dirty/imap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 IMAP MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 IMAP MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.