Delete an email. Moves to Trash first; permanently deletes only if already in Trash.
AI agents call delete_email to permanently remove resources in ProtonMail MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes email data. While the first deletion moves to Trash (reversible), the second deletion from Trash is permanent and cannot be undone, meeting the Destructive category definition. The severity is high because loss of email data could impact communications, evidence retention, and user operations.
From the tool's definition Tool name is 'delete_email' and description states it 'Delete an email' and 'permanently deletes' when already in Trash, indicating irreversible deletion of data.
Attacks that exploit this kind of access
Delete an email. Moves to Trash first; permanently deletes only if already in Trash. It is categorised as a Destructive tool in the ProtonMail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ProtonMail MCP Server MCP server in PolicyLayer and add a rule for 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 ProtonMail MCP Server. Nothing to install.
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 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 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.
delete_email is provided by the ProtonMail MCP Server MCP server (ronamosa/protonmail-pro-mcp). 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 →