drive_copy · Gworkspace MCP: Risk & Policy

WHAT IT DOES

What drive_copy does on Gworkspace

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

WHY IT NEEDS A POLICY

Why drive_copy needs a policy

The drive_copy tool creates a new file by duplicating an existing one, which is a reversible Write operation. It does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial).

From the tool's definition Tool description states "Copy a Drive file (spreadsheet, doc, etc). Returns the new file ID and URL." This action creates a new file resource in Google Drive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_copy Rate-limited

drive_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_copy": {
      "limits": [
        {
          "counter": "drive_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 Gworkspace, so you can run agents against it safely.

FAQ

Questions about drive_copy

What does the drive_copy tool do? +

Copy a Drive file (spreadsheet, doc, etc). Returns the new file ID and URL. It is categorised as a Write tool in the Gworkspace 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_copy? +

Register the Gworkspace MCP server in PolicyLayer and add a rule for drive_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 Gworkspace. Nothing to install.

What risk level is drive_copy? +

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

Can I rate-limit drive_copy? +

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

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

drive_copy is provided by the Gworkspace MCP server (leoonic/gworkspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.