GOOGLESUPER_MOVE_TO_TRASH
Moves an existing, non-deleted email message to the trash for the specified user.
This record as markdown: /tools/googlesuper/googlesuper-move-to-trash.md
What GOOGLESUPER_MOVE_TO_TRASH does on Google Super
AI agents call GOOGLESUPER_MOVE_TO_TRASH to permanently remove resources in Google Super, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
user_id | string | — | User's email address or 'me' for the authenticated user. |
message_id | string | — | Identifier of the email message to move to trash. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_MOVE_TO_TRASH is rated Critical
Moving an email to trash is effectively a deletion action — while technically recoverable from trash within a window, it removes the message from the inbox and is considered a destructive operation. Misuse by an AI agent could result in loss of important communications. The 'non-deleted' qualifier implies this is the primary deletion pathway.
From the tool's definition Moves an existing, non-deleted email message to the trash for the specified user.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_MOVE_TO_TRASH safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_MOVE_TO_TRASH, this is the rule to start with:
GOOGLESUPER_MOVE_TO_TRASH 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 Google Super, apply this rule, and every GOOGLESUPER_MOVE_TO_TRASH call is checked against it from then on.
Questions about GOOGLESUPER_MOVE_TO_TRASH
Moves an existing, non-deleted email message to the trash for the specified user. It is categorised as a Destructive tool in the Google Super MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
GOOGLESUPER_MOVE_TO_TRASH accepts 2 parameters: user_id, message_id. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_MOVE_TO_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 Google Super. Nothing to install.
GOOGLESUPER_MOVE_TO_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 GOOGLESUPER_MOVE_TO_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 GOOGLESUPER_MOVE_TO_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.
GOOGLESUPER_MOVE_TO_TRASH is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
Across the catalogue