Move one or more Google Drive files to trash. Use dryRun to preview which files would be trashed.
AI agents call gdrive_trash_files to permanently remove resources in Google Drive MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Trashing files in Google Drive removes them from their current location and places them in trash, which is effectively a destructive action. While files can technically be restored from trash, this is a bulk operation ('one or more files') that removes data from its active state. The blast radius is high because an AI agent could trash many files at once.
From the tool's definition Move one or more Google Drive files to trash
Attacks that exploit this kind of access
Move one or more Google Drive files to trash. Use dryRun to preview which files would be trashed. It is categorised as a Destructive tool in the Google Drive MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for gdrive_trash_files: 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 Drive MCP Server. Nothing to install.
gdrive_trash_files 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 gdrive_trash_files 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 gdrive_trash_files. 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.
gdrive_trash_files is provided by the Google Drive MCP Server MCP server (konashevich/mcp-gdrive). 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 →