Delete emails permanently. This action cannot be undone. Prefer move_emails to Trash mailbox for safer deletion — use this only when permanent deletion is explicitly requested.
AI agents call delete_emails to permanently remove resources in JMAP MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently and irreversibly deletes emails, which matches the Destructive category definition. The description explicitly states 'cannot be undone,' confirming irreversibility. Severity is high because deleted emails cannot be recovered and the blast radius includes permanent loss of user data. The confidence is very high due to clear language and intentional design documentation.
From the tool's definition Delete emails permanently. This action cannot be undone.
Documented attack patterns abuse exactly the kind of access delete_emails gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JMAP MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_emails:
{
"version": "1",
"default": "deny",
"hide": [
"delete_emails"
]
}delete_emails 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.
Delete emails permanently. This action cannot be undone. Prefer move_emails to Trash mailbox for safer deletion — use this only when permanent deletion is explicitly requested. It is categorised as a Destructive tool in the JMAP MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the JMAP MCP server in PolicyLayer and add a rule for delete_emails: 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 JMAP MCP. Nothing to install.
delete_emails 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 delete_emails 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 delete_emails. 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.
delete_emails is provided by the JMAP MCP server (wyattjoh/jmap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 JMAP MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 JMAP MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.