shutdown_instance

Power off a Linode instance

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server

High RISK CLASS

Category Execute

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/shutdown-instance.md

WHAT IT DOES

What shutdown_instance does on Linode MCP Server

AI agents invoke shutdown_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.

RISK

Why shutdown_instance is rated High

Powering off a cloud instance is an operational action with significant blast radius (service disruption, downtime) but is reversible (instance can be powered back on), placing it in Execute rather than Destructive. Misuse by an AI agent could take critical workloads offline.

From the tool's definition 'Power off a Linode instance' — shuts down a running compute instance, an external operational effect that disrupts running workloads but does not delete data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

shutdown_instance Rate-limited

shutdown_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": {
    "shutdown_instance": {
      "limits": [
        {
          "counter": "shutdown_instance_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about shutdown_instance

What does the shutdown_instance tool do? +

Power off a Linode 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 shutdown_instance? +

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

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

Can I rate-limit shutdown_instance? +

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

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

shutdown_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 → High-risk tools on this server →

Across the catalogue

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

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →