# list_instances

A read tool on the Linode MCP Server MCP server.

Agent View of the PolicyLayer registry record for `list_instances`. HTML page: https://policylayer.com/tools/komer3-linode-mcp/list-instances

## Facts

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

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

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

## Why list_instances is rated Low

This tool retrieves or enumerates Linode instances without modifying state. While the description is empty, the name and context clearly indicate a read-only listing operation. No side effects are expected from querying instance information.

From the tool's own definition: "Tool name 'list_instances' with no destructive or modification keywords; sibling tools include 'create', 'delete', 'reboot' which are distinguished from this tool, and server description explicitly lists 'listing' as a separate capability from 'creating,…"

## Use case

AI agents call list_instances to retrieve information from Linode MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_instances": {}
  }
}
```

## Other tools on Linode MCP Server (6)

- `delete_instance` — Destructive — https://policylayer.com/tools/komer3-linode-mcp/delete-instance.md
- `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_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