AI agents call trash_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.
Trashing emails removes them from the user's inbox and moves them to Trash. While Gmail technically allows recovery from Trash within 30 days, this is a bulk destructive operation that could cause significant data loss if misused by an AI agent. The tool operates on a list of emails, amplifying the blast radius.
From the tool's definition 'Thrash a list of emails' — moves emails to trash, which is a destructive/irreversible-in-practice operation removing emails from inbox; operates on a list (bulk action)
Documented attack patterns abuse exactly the kind of access trash_emails gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gmail, and nothing reaches the server without passing your rules. This is the rule we recommend for trash_emails:
{
"version": "1",
"default": "deny",
"hide": [
"trash_emails"
]
} trash_emails disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Thrash a list of emails. 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 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. Nothing to install.
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 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 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.
trash_emails is provided by the Gmail MCP server (ivanlhz/gmail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gmail, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Gmail tools catalogued and risk-classified — across an index of 43,000+ MCP servers.