clone_disk

Clone a disk for a Linode instance

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server

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/takashito-linode-mcp-server/clone-disk.md

WHAT IT DOES

What clone_disk does on Linode MCP Server

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

RISK

Why clone_disk is rated Medium

Cloning a disk creates a new copy of an existing disk, which is a reversible write/create operation. It does not delete or overwrite existing data, and it does not execute code. The blast radius is medium since it consumes storage resources and could be misused to duplicate sensitive disk contents.

From the tool's definition Clone a disk for a Linode instance

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clone_disk safely

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

clone_disk Rate-limited

clone_disk 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": {
    "clone_disk": {
      "limits": [
        {
          "counter": "clone_disk_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 Linode MCP Server, apply this rule, and every clone_disk call is checked against it from then on.

FAQ

Questions about clone_disk

What does the clone_disk tool do? +

Clone a disk for a Linode instance. It is categorised as a Write tool in the Linode MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on clone_disk? +

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

What risk level is clone_disk? +

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

Can I rate-limit clone_disk? +

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

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

clone_disk is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Linode MCP Server, and thousands of servers like it.

This server

All 416 Linode MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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