# delete_instance

A destructive tool on the Linode MCP Server MCP server.

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

## Facts

- Tool: `delete_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: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

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

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

## Why delete_instance is rated Critical

delete_instance removes cloud computing instances—a permanent, non-reversible action. An AI agent misuse could terminate production workloads, causing significant downtime and data loss. This qualifies as Destructive (most severe applicable category), not merely Execute, because the effect cannot be undone and the blast radius is infrastructure-wide.

From the tool's own definition: "Tool name 'delete_instance' combined with server description that explicitly mentions 'deleting Linode instances' indicates irreversible deletion of cloud infrastructure resources."

## Use case

AI agents call delete_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.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_instance"
  ]
}
```

## Other tools on Linode MCP Server (6)

- `reboot_instance` — Execute — https://policylayer.com/tools/komer3-linode-mcp/reboot-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