# reboot_instance

A execute tool on the Linode MCP Server MCP server.

Agent View of the PolicyLayer registry record for `reboot_instance`. HTML page: https://policylayer.com/tools/komer3-linode-mcp/reboot-instance

## Facts

- Tool: `reboot_instance`
- Server: Linode MCP Server (`komer3/linode-mcp`) — https://policylayer.com/tools/komer3-linode-mcp.md
- Homepage: https://github.com/komer3/linode-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "reboot_instance",
    "arguments": {}
  }
}
```

## Why reboot_instance is rated High

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 own definition: "Tool name 'reboot_instance' on a server described as managing Linode cloud resources including 'rebooting Linode instances'"

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Linode MCP Server:

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

## Other tools on Linode MCP Server (6)

- `delete_instance` — Destructive — https://policylayer.com/tools/komer3-linode-mcp/delete-instance.md
- `get_instance` — Read — https://policylayer.com/tools/komer3-linode-mcp/get-instance.md
- `list_instance_types` — Read — https://policylayer.com/tools/komer3-linode-mcp/list-instance-types.md
- `list_instances` — Read — https://policylayer.com/tools/komer3-linode-mcp/list-instances.md
- `list_regions` — Read — https://policylayer.com/tools/komer3-linode-mcp/list-regions.md
- `create_instance` — Write — https://policylayer.com/tools/komer3-linode-mcp/create-instance.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=komer3-linode-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/komer3-linode-mcp