Trash or delete a file
AI agents call drive_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 files cannot be undone (even if moved to trash, it is removed from the user's active file system). This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone'. Severity is high because an AI agent with access to this tool could delete critical documents, folders, or collaborative files, causing significant data loss.
From the tool's definition Tool name is 'drive_delete' and description states 'Trash or delete a file' — this irreversibly removes data from Google Drive.
Attacks that exploit this kind of access
Trash or delete 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_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_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_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_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_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 →