Move a Google Drive file or folder to trash (or permanently delete it). Use search_drive first to find the file ID.
AI agents call trash_file to permanently remove resources in Google — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes or moves to trash Google Drive files and folders. Even though trashing is technically reversible (files remain in trash for a period), the tool explicitly states it can 'permanently delete', which is irreversible. The capability to remove access to data and permanently destroy it qualifies as Destructive.
From the tool's definition Move a Google Drive file or folder to trash (or permanently delete it)
Attacks that exploit this kind of access
Move a Google Drive file or folder to trash (or permanently delete it). Use search_drive first to find the file ID. It is categorised as a Destructive tool in the Google MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google MCP server in PolicyLayer and add a rule for trash_file: 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. Nothing to install.
trash_file 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_file 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_file. 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_file is provided by the Google MCP server (ztgluis/google-mcp). 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 →