clone_instance

Clone 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-instance.md

WHAT IT DOES

What clone_instance does on Linode MCP Server

AI agents use clone_instance 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_instance is rated Medium

Cloning creates a new compute instance (a copy of an existing one), which is a reversible write operation — it does not delete or overwrite data. However, the blast radius is high because it spins up a full cloud instance, potentially incurring significant resource costs and consuming quota.

From the tool's definition Clone a Linode instance

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clone_instance 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_instance, this is the rule to start with:

clone_instance Rate-limited

clone_instance 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_instance": {
      "limits": [
        {
          "counter": "clone_instance_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_instance call is checked against it from then on.

FAQ

Questions about clone_instance

What does the clone_instance tool do? +

Clone 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_instance? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for clone_instance: 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_instance? +

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

Can I rate-limit clone_instance? +

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

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

clone_instance 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 →