copy_doc · Google MCP: Risk & Policy

WHAT IT DOES

What copy_doc does on Google

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

WHY IT NEEDS A POLICY

Why copy_doc needs a policy

This tool creates new data (a duplicate document) and modifies metadata (name, location), which are classic Write operations. While the copy operation itself is reversible (the duplicate can be deleted), it modifies the user's Drive state and could spam or clutter if misused by an agent.

From the tool's definition copy_doc creates a new document by duplicating an existing Google Doc, with optional rename and folder move operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_doc Rate-limited

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

FAQ

Questions about copy_doc

What does the copy_doc tool do? +

Copy an existing Google Doc. Optionally rename and/or move to a different folder. It is categorised as a Write tool in the Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on copy_doc? +

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

What risk level is copy_doc? +

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

Can I rate-limit copy_doc? +

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

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

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