Permanently delete a file (cannot be recovered).
AI agents call permanently_delete_file to permanently remove resources in Google Docs MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data without possibility of recovery, meeting the Destructive category definition. The high severity reflects significant blast radius if an AI agent accidentally or maliciously deletes important Google Docs or Drive files belonging to the user. Confidence is very high due to explicit language about permanent deletion and non-recoverability in both name and description.
From the tool's definition Tool name 'permanently_delete_file' and description states 'Permanently delete a file (cannot be recovered)' - irreversible deletion operation.
Attacks that exploit this kind of access
Permanently delete a file (cannot be recovered). It is categorised as a Destructive tool in the Google Docs MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Docs MCP Server MCP server in PolicyLayer and add a rule for permanently_delete_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 Docs MCP Server. Nothing to install.
permanently_delete_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 permanently_delete_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 permanently_delete_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.
permanently_delete_file is provided by the Google Docs MCP Server MCP server (nickweedon/google-docs-mcp-docker). 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 →