copy_file · Google Connections MCP: Risk & Policy

WHAT IT DOES

What copy_file does on Google Connections

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

WHY IT NEEDS A POLICY

Why copy_file needs a policy

This tool creates a new copy of a file, which is a reversible modification operation (Write category). It does not execute code or trigger external operations beyond file duplication. Severity is medium because misuse could duplicate sensitive files to unintended locations or with misleading names, but the action is reversible via deletion.

From the tool's definition copy_file: 'Copy a file. Cannot copy folders. Optionally specify new name and/or destination folder.' Creates a new file resource.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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

FAQ

Questions about copy_file

What does the copy_file tool do? +

Copy a file. Cannot copy folders. Optionally specify new name and/or destination folder. It is categorised as a Write tool in the Google Connections 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 Google Connections 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 Google Connections. 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 Google Connections MCP server (michaelzrork/google-connections-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.