DESTRUCTIVE. Defaults to dry-run; pass confirm=true to apply.
AI agents call email_move to permanently remove resources in MCP Email Service — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool is explicitly labeled DESTRUCTIVE. Moving emails reorganizes them in a way that may be difficult to reverse (especially across accounts or folders), and the dry-run default with a required confirm=true flag indicates the operation has significant, potentially irreversible side effects. Misuse by an AI agent could result in mass reorganization or loss of email organization across multiple accounts.
From the tool's definition DESTRUCTIVE. Defaults to dry-run; pass confirm=true to apply.
Documented attack patterns abuse exactly the kind of access email_move gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Email Service, and nothing reaches the server without passing your rules. This is the rule we recommend for email_move:
{
"version": "1",
"default": "deny",
"hide": [
"email_move"
]
}email_move disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
DESTRUCTIVE. Defaults to dry-run; pass confirm=true to apply. It is categorised as a Destructive tool in the MCP Email Service MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Email Service MCP server in PolicyLayer and add a rule for email_move: 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 MCP Email Service. Nothing to install.
email_move is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the email_move 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 email_move. 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.
email_move is provided by the MCP Email Service MCP server (leeguooooo/mailbox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Email Service, 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.
16 MCP Email Service tools catalogued and risk-classified — across an index of 43,000+ MCP servers.