delete_file_forever
PERMANENTLY deletes a file, BYPASSING the trash — there is no undo, no 30-day grace period, and a folder takes every descendant with it. This is NOT the same as trash_file: when a user says 'delete', they almost always mean the reversible trash — use trash_file unless they explicitly confirmed pe...
This record as markdown: /tools/a1-x-tech-mcp-google-drive/delete-file-forever.md
What delete_file_forever does on Mcp Google Drive
AI agents call delete_file_forever 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 |
|---|---|---|---|
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 delete_file_forever is rated Critical
An AI agent that decides to call delete_file_forever 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 delete_file_forever 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 delete_file_forever, this is the rule to start with:
delete_file_forever 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 delete_file_forever call is checked against it from then on.
Questions about delete_file_forever
PERMANENTLY deletes a file, BYPASSING the trash — there is no undo, no 30-day grace period, and a folder takes every descendant with it. This is NOT the same as trash_file: when a user says 'delete', they almost always mean the reversible trash — use trash_file unless they explicitly confirmed permanent, unrecoverable deletion. Requires ownership (or organizer on a shared drive). Returns {ok:true} on success (the API responds with an empty 204). 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.
delete_file_forever accepts 1 parameter: file_id. Required: 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 delete_file_forever: 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.
delete_file_forever 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 delete_file_forever 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 delete_file_forever. 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.
delete_file_forever 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