drive_batch_copy · Google Drive MCP Server MCP

WHAT IT DOES

What drive_batch_copy does on Google Drive MCP Server

AI agents use drive_batch_copy to create or update resources in Google Drive MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive MCP Server environment.

WHY IT NEEDS A POLICY

Why drive_batch_copy needs a policy

Copying files creates new data objects in the destination folder, which is a reversible write operation. While not destructive (originals remain), it modifies the file system state by creating duplicates. Severity is medium because bulk copying could consume storage quota and create unwanted duplicates, but the operation is reversible via deletion.

From the tool's definition Tool name 'drive_batch_copy' and description 'Copy multiple files to a destination folder' indicate creation of new file copies. The batch operation on 'multiple files' amplifies the scope of data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_batch_copy Rate-limited

drive_batch_copy stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "drive_batch_copy": {
      "limits": [
        {
          "counter": "drive_batch_copy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Drive MCP Server, so you can run agents against it safely.

FAQ

Questions about drive_batch_copy

What does the drive_batch_copy tool do? +

Copy multiple files to a destination folder. It is categorised as a Write tool in the Google Drive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on drive_batch_copy? +

Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for drive_batch_copy: 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_copy? +

drive_batch_copy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit drive_batch_copy? +

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

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

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