list_instances

A read tool on the Linode MCP server.

SERVERLinode MCP Server SOURCEkomer3/linode-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/komer3-linode-mcp/list-instances.md

WHAT IT DOES

What list_instances does on Linode MCP Server

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.

RISK

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 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,…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_instances Allowed

list_instances is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY 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 list_instances call is checked against it from then on.

FAQ

Questions about list_instances

What does the list_instances tool do? +

list_instances is a read tool on the Linode MCP Server MCP server. It is categorised as a Read tool in the Linode MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_instances? +

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

list_instances is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_instances? +

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

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

list_instances is provided by the Linode MCP Server MCP server (komer3/linode-mcp). 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 7 Linode MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →