trash_gmail_messages
AI agents call trash_gmail_messages 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 emails is a near-irreversible destructive action (Gmail trash auto-purges after 30 days, and users may not notice). The tool name clearly implies deletion/trashing of Gmail messages. While technically recoverable within 30 days, it is conventionally classified as Destructive due to potential data loss. The plural 'messages' suggests bulk operation, increasing blast radius to high.
From the tool's definition Tool name 'trash_gmail_messages' — 'trash' indicates moving messages to trash, which is a deletion action. Sibling tools include 'bulk_archive_gmail', suggesting this tool may operate on multiple messages.
Attacks that exploit this kind of access
trash_gmail_messages. 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 trash_gmail_messages: 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.
trash_gmail_messages 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_gmail_messages 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_gmail_messages. 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_gmail_messages is provided by the Gmail MCP Server MCP server (stevesimpson418/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 →