Critical Risk →

drive_deleteFile

Delete a file (moves to trash by default).

How to control drive_deleteFile ↓

What drive_deleteFile does on Google MCP Remote

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

Critical Risk

Why drive_deleteFile needs a policy

This tool removes data from Google Drive. Although moved to trash rather than permanently purged, deletion is irreversible from the user's working perspective and represents a destructive action. An AI agent with access could delete critical files, presentations, documents, or shared resources.

From the tool's definition Tool name 'drive_deleteFile' and description 'Delete a file (moves to trash by default)' explicitly indicate irreversible removal of data. Even though trash may allow recovery, the primary action is deletion without user confirmation in the tool interface.

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

How to control drive_deleteFile

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

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

drive_deleteFile 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 Google MCP Remote — 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 drive_deleteFile

What does the drive_deleteFile tool do? +

Delete a file (moves to trash by default). It is categorised as a Destructive tool in the Google MCP Remote 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 drive_deleteFile? +

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

What risk level is drive_deleteFile? +

drive_deleteFile 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 drive_deleteFile? +

Yes. Add a rate_limit block to the drive_deleteFile 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 drive_deleteFile completely? +

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

drive_deleteFile is provided by the Google MCP Remote MCP server (vakharwalad23/google-mcp-remote). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google MCP Remote tool call.

Start from Google MCP Remote, 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.

35 Google MCP Remote 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.