drive_batch_delete

Delete multiple files or folders at once

Server Google Drive MCP Server rishipradeep-think41/google-drive-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What drive_batch_delete does on Google Drive MCP Server

AI agents call drive_batch_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.

Why drive_batch_delete needs a policy

Deletion of files is irreversible and cannot be undone. The batch capability amplifies the risk by allowing deletion of multiple items simultaneously, resulting in potential massive data loss. This is the most severe category applicable and warrants critical severity due to the high blast radius of mistaken or malicious bulk deletion.

From the tool's definition Tool name is 'drive_batch_delete' and description states 'Delete multiple files or folders at once'. The verb 'delete' combined with batch operation (multiple files) and the irreversible nature of file deletion indicate a destructive action.

Questions about drive_batch_delete

What does the drive_batch_delete tool do? +

Delete multiple files or folders at once. 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.

How do I enforce a policy on drive_batch_delete? +

Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for drive_batch_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.

What risk level is drive_batch_delete? +

drive_batch_delete 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_batch_delete? +

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

How do I block drive_batch_delete completely? +

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

What MCP server provides drive_batch_delete? +

drive_batch_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.

// THE FULL RECORD

drive_batch_delete is one line of Google Drive MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.