Critical Risk →

gd_delete_drive

Permanently delete a shared drive. The drive must be empty (no files) before it can be deleted. This action is irreversible.

Part of the Google Drive server.

gd_delete_drive can permanently delete data in Google Drive, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE GOOGLE DRIVE →

Free to start. No card required.

AI agents may call gd_delete_drive to permanently remove or destroy resources in Google Drive. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call gd_delete_drive in a loop, permanently destroying resources in Google Drive. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

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

See the full Google Drive policy for all 44 tools.

Get this rule live on your own Google Drive server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY GOOGLE DRIVE →

View all 44 tools →

These attack patterns abuse exactly the kind of access gd_delete_drive gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so gd_delete_drive only ever does what you allow.

SECURE GOOGLE DRIVE →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the gd_delete_drive tool do? +

Permanently delete a shared drive. The drive must be empty (no files) before it can be deleted. This action is irreversible.. It is categorised as a Destructive tool in the Google Drive 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 gd_delete_drive? +

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

What risk level is gd_delete_drive? +

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

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

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

gd_delete_drive is provided by the Google Drive MCP server (@modelcontextprotocol/server-gdrive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Drive tool call.

Deterministic rules across all 44 Google Drive tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.