Delete a specific version of a file
AI agents call drive_versions_delete 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.
Deletion of file versions cannot be undone and removes access to prior states of a document. Although it does not delete the entire file, it permanently destroys a version record. This meets the Destructive criterion: irreversibly deletes data that cannot be recovered.
From the tool's definition Tool name includes 'delete' and description states 'Delete a specific version of a file' — this irreversibly removes a historical version of a file, preventing recovery of that state.
Attacks that exploit this kind of access
Delete a specific version of a file. 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 drive_versions_delete: 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.
drive_versions_delete 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 drive_versions_delete 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 drive_versions_delete. 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.
drive_versions_delete is provided by the Google Drive MCP Server MCP server (rishipradeep-think41/google-drive-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 →