Permanently deletes multiple emails in batches
AI agents call batch_delete_emails to permanently remove resources in Gmail — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data at scale (batch deletion). Once executed, emails cannot be recovered through normal means. The blast radius is high because a single misconfigured batch operation could delete large volumes of user emails. This is Destructive rather than Execute because the operation is inherently destructive and cannot be undone, not just a command that happens to have side effects.
From the tool's definition Tool name explicitly states 'batch_delete_emails' and description confirms 'Permanently deletes multiple emails in batches'. The word 'Permanently' indicates irreversible deletion.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Permanently deletes multiple emails in batches. It is categorised as a Destructive tool in the Gmail MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gmail MCP server in PolicyLayer and add a rule for batch_delete_emails: 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 Gmail. Nothing to install.
batch_delete_emails 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 batch_delete_emails 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 batch_delete_emails. 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.
batch_delete_emails is provided by the Gmail MCP server (pouyanafisi/gmail-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 →