copy_object_safe · Storage MCP: Risk & Policy

WHAT IT DOES

What copy_object_safe does on Storage

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

WHY IT NEEDS A POLICY

Why copy_object_safe needs a policy

This tool creates or modifies data in GCS by copying objects to new locations. It is reversible (the copy can be deleted), so it falls under Write rather than Destructive. The safety mechanism prevents accidental overwrites. Severity is medium because misuse could create unwanted copies consuming storage, but the operation is non-destructive and could be cleaned up.

From the tool's definition Tool name 'copy_object_safe' and description 'Copies an object to a new destination' indicates a data modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_object_safe Rate-limited

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

FAQ

Questions about copy_object_safe

What does the copy_object_safe tool do? +

Copies an object to a new destination. Fails if an object already exists at the destination. It is categorised as a Write tool in the Storage 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_object_safe? +

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

What risk level is copy_object_safe? +

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

Can I rate-limit copy_object_safe? +

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

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

copy_object_safe is provided by the Storage MCP server (@google-cloud/storage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.