trash_file
action=trash moves a file (or folder, with everything inside) to the Drive trash; action=restore brings it back. Trashing is REVERSIBLE — the file stays recoverable until the trash auto-purges it after ~30 days — and is the safe default whenever a user asks to 'delete' something: only use delete_...
This record as markdown: /tools/a1-x-tech-mcp-google-drive/trash-file.md
What trash_file does on Mcp Google Drive
AI agents call trash_file to permanently remove resources in Mcp Google Drive, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | trash = move to the trash (reversible); restore = take it back out. |
file_id | string | Yes | The file id — the long id from the Drive URL (drive.google.com/file/d/<fileId> or docs.google.com/.../d/<fileId>/edit) or from search_files/get_file output. Fol |
Parameters from the server's own tool schema.
Why trash_file is rated Critical
An AI agent that decides to call trash_file doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Google Drive is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs trash_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trash_file, this is the rule to start with:
trash_file 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 Mcp Google Drive, apply this rule, and every trash_file call is checked against it from then on.
Questions about trash_file
action=trash moves a file (or folder, with everything inside) to the Drive trash; action=restore brings it back. Trashing is REVERSIBLE — the file stays recoverable until the trash auto-purges it after ~30 days — and is the safe default whenever a user asks to 'delete' something: only use delete_file_forever when they explicitly want it gone beyond recovery. Trashed files disappear from search_files unless include_trashed=true. Only the owner (or a shared-drive member with the right role) can trash; restore puts the file back at its old parent. Returns id, name, trashed and explicitlyTrashed. It is categorised as a Destructive tool in the Mcp Google Drive MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
trash_file accepts 2 parameters: action, file_id. Required: action, file_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Drive 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 Mcp Google Drive. 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 Mcp Google Drive MCP server (@a1-x-tech/mcp-google-drive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Drive, and thousands of servers like it.
Across the catalogue