Update an existing draft by deleting old and creating new
AI agents use update_draft to create or update resources in IMAP Email MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your IMAP Email MCP Server environment.
This tool creates or modifies email drafts, which are not yet sent and can be further edited or deleted. While it involves deletion logic internally, the net effect is reversible modification of draft state rather than permanent destruction. The primary action is write-class (modifying data).
From the tool's definition Tool description states 'Update an existing draft by deleting old and creating new' - this modifies draft messages reversibly. The name 'update_draft' and description explicitly indicate creating/modifying email drafts without sending them.
Documented attack patterns abuse exactly the kind of access update_draft gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and IMAP Email MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_draft:
{
"version": "1",
"default": "deny",
"tools": {
"update_draft": {
"limits": [
{
"counter": "update_draft_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_draft 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.
Update an existing draft by deleting old and creating new. It is categorised as a Write tool in the IMAP Email MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the IMAP Email MCP Server MCP server in PolicyLayer and add a rule for update_draft: 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 Email MCP Server. Nothing to install.
update_draft 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 update_draft 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 update_draft. 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.
update_draft is provided by the IMAP Email MCP Server MCP server (jdickey1/imap-email-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from IMAP Email MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 IMAP Email MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.