copy_file

Copy a file.

SERVERMcp Google Docs SOURCEdev-ithitchhiker/mcp-google-docs

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-ithitchhiker-mcp-google-docs/copy-file.md

WHAT IT DOES

What copy_file does on Mcp Google Docs

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

RISK

Why copy_file is rated Medium

Copying a file creates a new resource but is reversible (the copy can be deleted). This is a Write operation rather than Read (it modifies the Drive by creating new content) or Destructive (copying doesn't remove or irreversibly alter the original). The severity is medium because unintended file copies could bloat storage or create confusion, but the impact is limited to the user's own Drive and remains undoable.

From the tool's definition Tool is named 'copy_file' with description 'Copy a file.' Operating on Google Drive files, copying creates new data/resources reversibly.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs copy_file safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For copy_file, this is the rule to start with:

copy_file Rate-limited

copy_file 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_file": {
      "limits": [
        {
          "counter": "copy_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Docs, apply this rule, and every copy_file call is checked against it from then on.

FAQ

Questions about copy_file

What does the copy_file tool do? +

Copy a file. It is categorised as a Write tool in the Mcp Google Docs 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_file? +

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

What risk level is copy_file? +

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

Can I rate-limit copy_file? +

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

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

copy_file is provided by the Mcp Google Docs MCP server (dev-ithitchhiker/mcp-google-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Google Docs, and thousands of servers like it.

This server

All 55 Mcp Google Docs tools →

Across the catalogue

write_file on 0sec → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →