Move multiple emails to Trash at once by adding the TRASH label and removing INBOX.
AI agents call batch_trash_emails to permanently remove resources in Gmail MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Trashing multiple emails at once is a bulk destructive action that removes emails from the inbox. While technically emails may sit in Trash before permanent deletion, this is effectively irreversible in practice for an AI agent (user may not notice or recover them), and the batch nature amplifies the blast radius significantly.
From the tool's definition Move multiple emails to Trash at once by adding the TRASH label and removing INBOX
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Move multiple emails to Trash at once by adding the TRASH label and removing INBOX. It is categorised as a Destructive tool in the Gmail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for batch_trash_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 MCP Server. Nothing to install.
batch_trash_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_trash_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_trash_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_trash_emails is provided by the Gmail MCP Server MCP server (neutral-stage/gmail-mcp-server). 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 →