Move every message in a thread to Trash via
AI agents call gmail_thread_trash to permanently remove resources in Mcp Gmail — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Moving every message in a thread to Trash is a bulk destructive operation. While Gmail Trash is technically recoverable within 30 days, trashing an entire thread (potentially many messages) is a high-blast-radius action that is effectively irreversible from a workflow perspective and can cause significant data loss if misused by an AI agent. The 'every message in a thread' scope amplifies severity.
From the tool's definition Move every message in a thread to Trash
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Move every message in a thread to Trash via. It is categorised as a Destructive tool in the Mcp Gmail MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for gmail_thread_trash: 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 Mcp Gmail. Nothing to install.
gmail_thread_trash 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 gmail_thread_trash 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 gmail_thread_trash. 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.
gmail_thread_trash is provided by the Mcp Gmail MCP server (knowledgeislands/mcp-gmail). 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 →