AI agents use move_email to create or update resources in Apple Mail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Mail MCP Server environment.
Moving emails between mailboxes is a reversible operation that modifies email organization state but does not delete data irreversibly. It falls under Write (state modification) rather than Destructive (irreversible deletion). Severity is medium because misconfiguration could cause emails to be moved to wrong folders, impacting workflow, but changes are undoable via moving back to original location.
From the tool's definition Tool name 'move_email' indicates modification of email state/location. Sibling tools include 'compose_email', 'create_mailbox', 'forward_email', 'export_emails'—all write-class operations.
Documented attack patterns abuse exactly the kind of access move_email gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Mail MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for move_email:
{
"version": "1",
"default": "deny",
"tools": {
"move_email": {
"limits": [
{
"counter": "move_email_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} move_email 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.
move_email. It is categorised as a Write tool in the Apple Mail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apple Mail MCP Server MCP server in PolicyLayer and add a rule for move_email: 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 Apple Mail MCP Server. Nothing to install.
move_email 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 move_email 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 move_email. 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.
move_email is provided by the Apple Mail MCP Server MCP server (patrickfreyer/apple-mail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 Apple Mail MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
26 Apple Mail MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.