Delete a folder/mailbox. The folder must be empty.
AI agents call imap_delete_folder to permanently remove resources in Email MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a mailbox/folder is an irreversible destructive action that cannot be undone. Even though the constraint requires the folder to be empty, successful execution permanently removes the folder and all associated metadata/organization. This places it in the Destructive category rather than Write (which is reversible).
From the tool's definition Tool name explicitly states 'delete_folder' and description confirms 'Delete a folder/mailbox.' This is an irreversible deletion operation that removes email storage and its organizational structure.
Attacks that exploit this kind of access
Delete a folder/mailbox. The folder must be empty. It is categorised as a Destructive tool in the Email MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Email MCP Server MCP server in PolicyLayer and add a rule for imap_delete_folder: 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 Email MCP Server. Nothing to install.
imap_delete_folder 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 imap_delete_folder 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 imap_delete_folder. 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.
imap_delete_folder is provided by the Email MCP Server MCP server (sventern/mcp_email). 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 →