drive_delete_file
Delete a file from Google Drive
This record as markdown: /tools/io-github-alifanov-scopegate/drive-delete-file.md
What drive_delete_file does on ScopeGate
AI agents call drive_delete_file to permanently remove resources in ScopeGate, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why drive_delete_file is rated Critical
Deleting a file from Google Drive is an irreversible destructive action that permanently removes data. Once deleted, the file cannot be recovered through normal means, making this a Destructive category tool. Severity is high because an agent misusing this tool could delete critical user documents, but not critical (not financial/infrastructure-level).
From the tool's definition Tool name is 'drive_delete_file' and description states 'Delete a file from Google Drive'. The verb 'delete' combined with a persistent storage system (Google Drive) indicates irreversible data loss.
Attacks that exploit this kind of access
The rule that runs drive_delete_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drive_delete_file, this is the rule to start with:
drive_delete_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 ScopeGate, apply this rule, and every drive_delete_file call is checked against it from then on.
Questions about drive_delete_file
Delete a file from Google Drive. It is categorised as a Destructive tool in the ScopeGate MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ScopeGate MCP server in PolicyLayer and add a rule for drive_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 ScopeGate. Nothing to install.
drive_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 drive_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 drive_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.
drive_delete_file is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
Across the catalogue