copy_drive_notebook · Pypi:colab Drive MCP: Risk & Policy

WHAT IT DOES

What copy_drive_notebook does on Pypi:colab Drive

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

WHY IT NEEDS A POLICY

Why copy_drive_notebook needs a policy

This tool creates a new notebook file by duplicating an existing one in Google Drive. This is a reversible write operation (the copy can be deleted). The blast radius is medium because a bad copy could consume storage quota or clutter the drive, but the operation is non-destructive and does not execute code, delete data, or affect financial systems.

From the tool's definition Tool description states "Copy a notebook file in Google Drive" — copying is a write operation that creates new data (a duplicate notebook). The explicit caveat "without executing it" clarifies that no code execution occurs, excluding Execute category.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_drive_notebook Rate-limited

copy_drive_notebook 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_drive_notebook": {
      "limits": [
        {
          "counter": "copy_drive_notebook_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 Pypi:colab Drive, so you can run agents against it safely.

FAQ

Questions about copy_drive_notebook

What does the copy_drive_notebook tool do? +

Copy a notebook file in Google Drive without executing it. It is categorised as a Write tool in the Pypi:colab Drive 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_drive_notebook? +

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

What risk level is copy_drive_notebook? +

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

Can I rate-limit copy_drive_notebook? +

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

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

copy_drive_notebook is provided by the Pypi:colab Drive MCP server (yummytastycode/colab-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.