trash-email
AI agents call trash-email 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 an email removes it from the inbox and places it in the trash folder, which is effectively a destructive operation — while technically recoverable within a window, it is an irreversible action from the user's perspective in automated contexts. The name combined with the Gmail server context makes this classification high-confidence.
From the tool's definition Tool name 'trash-email' strongly implies moving an email to trash, which is a destructive/irreversible-ish action; description is empty providing no additional context.
Attacks that exploit this kind of access
trash-email. 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-email: 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-email 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-email 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-email. 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-email is provided by the Gmail MCP Server MCP server (jmonsellier/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 →