imap_bulk_delete_by_search
AI agents call imap_bulk_delete_by_search 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.
Bulk deletion is irreversible and cannot be undone. The 'bulk' qualifier combined with 'delete' and search-based targeting means an AI agent could permanently destroy large volumes of emails across accounts with a single misguided operation. This poses critical risk despite the empty description, as the name alone is sufficiently clear about destructive intent. Destructive is more severe than Write, Execute, or Read.
From the tool's definition Tool name contains 'bulk_delete' which indicates irreversible deletion of data at scale. The server description mentions email access across multiple accounts.
Attacks that exploit this kind of access
imap_bulk_delete_by_search. 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_bulk_delete_by_search: 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_bulk_delete_by_search 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_bulk_delete_by_search 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_bulk_delete_by_search. 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_bulk_delete_by_search 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 →