reboot_instance · Linode MCP Server MCP: Risk & Policy

WHAT IT DOES

What reboot_instance does on Linode MCP Server

AI agents invoke reboot_instance to trigger actions in Linode MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why reboot_instance needs a policy

Rebooting an instance triggers an external operation (restart of a cloud VM) that causes downtime and disrupts running workloads. It is not purely destructive (data is not deleted) but it executes an action with significant operational impact. The server description explicitly mentions rebooting as a capability.

From the tool's definition Tool name 'reboot_instance' on a server described as managing Linode cloud resources including 'rebooting Linode instances'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reboot_instance Rate-limited

reboot_instance stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reboot_instance": {
      "limits": [
        {
          "counter": "reboot_instance_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Linode MCP Server, so you can run agents against it safely.

FAQ

Questions about reboot_instance

What does the reboot_instance tool do? +

reboot_instance. It is categorised as a Execute tool in the Linode MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reboot_instance? +

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

reboot_instance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit reboot_instance? +

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

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

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