Permanently delete an .eml file from disk and remove it from the index
AI agents call delete_email to permanently remove resources in Eml — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes email data from both storage and index. Email is often critical communication history that cannot be recovered once deleted. While not financial in nature, the permanent destruction of user data without undo capability places it in the Destructive category with high severity due to the potential loss of important correspondence, legal records, or compliance-relevant messages.
From the tool's definition Tool description states 'Permanently delete an .eml file from disk and remove it from the index' - the word 'Permanently' and 'delete' indicate irreversible data loss.
Attacks that exploit this kind of access
Permanently delete an .eml file from disk and remove it from the index. It is categorised as a Destructive tool in the Eml MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Eml 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 Eml. 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 Eml MCP server (miguelripoll23/eml-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 →