rebuild_instance

Rebuild a Linode instance

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/takashito-linode-mcp-server/rebuild-instance.md

WHAT IT DOES

What rebuild_instance does on Linode MCP Server

AI agents call rebuild_instance to permanently remove resources in Linode MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why rebuild_instance is rated Critical

Rebuilding a compute instance is a destructive operation that erases all existing data, configurations, and state on the instance. This cannot be undone. The blast radius is critical because an AI agent misusing this tool could destroy production workloads, databases, and all data hosted on the instance.

From the tool's definition 'Rebuild a Linode instance' — rebuilding a cloud instance wipes the existing disk/OS and reinstalls from scratch, irreversibly destroying all data on the instance.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

rebuild_instance Hidden

rebuild_instance is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "rebuild_instance"
  ]
}

RESTRICT 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 rebuild_instance call is checked against it from then on.

FAQ

Questions about rebuild_instance

What does the rebuild_instance tool do? +

Rebuild a Linode instance. It is categorised as a Destructive tool in the Linode MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on rebuild_instance? +

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

rebuild_instance is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit rebuild_instance? +

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

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

rebuild_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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →