trashMessage
Moves a Gmail message to Trash. This is the same as clicking Delete in the Gmail UI — reversible from the Trash folder for 30 days. Not a permanent delete.
This record as markdown: /tools/a-bonus-google-docs-mcp/trashmessage.md
What trashMessage does on Claude MCP x Google Docs
AI agents call trashMessage to permanently remove resources in Claude MCP x Google Docs, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why trashMessage is rated Critical
Although technically recoverable within 30 days, moving messages to trash is an irreversible data removal action in the immediate sense—messages disappear from the inbox and standard view. An AI agent calling this tool without proper safeguards could delete user messages that the user did not intend to delete, causing data loss.
From the tool's definition Tool name 'trashMessage' combined with description 'Moves a Gmail message to Trash' — explicitly performs deletion action.
Attacks that exploit this kind of access
The rule that runs trashMessage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude MCP x Google Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trashMessage, this is the rule to start with:
trashMessage is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude MCP x Google Docs, apply this rule, and every trashMessage call is checked against it from then on.
Questions about trashMessage
Moves a Gmail message to Trash. This is the same as clicking Delete in the Gmail UI — reversible from the Trash folder for 30 days. Not a permanent delete. It is categorised as a Destructive tool in the Claude MCP x Google Docs MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude MCP x Google Docs MCP server in PolicyLayer and add a rule for trashMessage: 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 Claude MCP x Google Docs. Nothing to install.
trashMessage 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 trashMessage 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 trashMessage. 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.
trashMessage is provided by the Claude MCP x Google Docs MCP server (a-bonus/google-docs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude MCP x Google Docs, and thousands of servers like it.
Across the catalogue