Delete an email by moving it to the Trash folder. Use the folder name and email UID.
AI agents call proton_delete_email to permanently remove resources in Proton MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes user data from active access and potentially from permanent storage. An AI agent with access to this tool could delete emails without user consent, causing loss of important communications. This is a high-severity destructive operation affecting personal data integrity.
From the tool's definition Tool name is 'proton_delete_email' and description states 'Delete an email by moving it to the Trash folder.' The word 'Delete' directly indicates a destructive operation.
Attacks that exploit this kind of access
Delete an email by moving it to the Trash folder. Use the folder name and email UID. It is categorised as a Destructive tool in the Proton MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Proton MCP Server MCP server in PolicyLayer and add a rule for proton_delete_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 Proton MCP Server. Nothing to install.
proton_delete_email 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 proton_delete_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 proton_delete_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.
proton_delete_email is provided by the Proton MCP Server MCP server (sugar-crash-studios/proton-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →