# list_instance_types

A read tool on the Linode MCP Server MCP server.

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

## Facts

- Tool: `list_instance_types`
- 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_instance_types",
    "arguments": {}
  }
}
```

## Why list_instance_types is rated Low

This tool retrieves or enumerates available Linode instance type configurations (likely CPU, RAM, pricing, etc.). Listing instance types has no side effects—it does not create, modify, delete, or execute anything. It is a safe informational query suitable for AI agents to call without risk.

From the tool's own definition: "Tool name 'list_instance_types' uses the verb 'list', indicating a retrieval operation. The sibling tools on this Linode server include 'list_instances' and 'list_regions', establishing a pattern where 'list_*' tools are read-only queries."

## Use case

AI agents call list_instance_types 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_instance_types": {}
  }
}
```

## 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_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