Critical Risk →

delete_drive_file_tool

Permanently delete a file from Google Drive.

How to control delete_drive_file_tool ↓

What delete_drive_file_tool does on Apps Script MCP

AI agents call delete_drive_file_tool to permanently remove resources in Apps Script MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_drive_file_tool needs a policy

This tool irreversibly removes data from Google Drive with no undo capability. The word 'Permanently' confirms the action cannot be reversed. While the blast radius is bounded to files the agent has permission to access, deletion of critical documents, spreadsheets, or dependent files could cause significant harm. Classified as Destructive (most severe) rather than Write because the operation is not reversible.

From the tool's definition Tool name explicitly states 'delete' and description states 'Permanently delete a file from Google Drive' — irreversible deletion of data.

Documented attack patterns abuse exactly the kind of access delete_drive_file_tool gives an agent:

How to control delete_drive_file_tool

PolicyLayer is an MCP gateway — it sits between your AI agents and Apps Script MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_drive_file_tool:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_drive_file_tool"
  ]
}

delete_drive_file_tool disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Apps Script MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_drive_file_tool

What does the delete_drive_file_tool tool do? +

Permanently delete a file from Google Drive. It is categorised as a Destructive tool in the Apps Script MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_drive_file_tool? +

Register the Apps Script MCP server in PolicyLayer and add a rule for delete_drive_file_tool: 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 Apps Script MCP. Nothing to install.

What risk level is delete_drive_file_tool? +

delete_drive_file_tool is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_drive_file_tool? +

Yes. Add a rate_limit block to the delete_drive_file_tool 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.

How do I block delete_drive_file_tool completely? +

Set action: deny in the PolicyLayer policy for delete_drive_file_tool. 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.

What MCP server provides delete_drive_file_tool? +

delete_drive_file_tool is provided by the Apps Script MCP server (sam-ent/google-automation-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Apps Script MCP tool call.

Start from Apps Script MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

60 Apps Script MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.