list_instance_types
AI agents call list_instance_types to retrieve information from Linode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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 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.
Attacks that exploit this kind of access
list_instance_types. It is categorised as a Read tool in the Linode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for list_instance_types: 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.
list_instance_types is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_instance_types 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.
Set action: deny in the PolicyLayer policy for list_instance_types. 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.
list_instance_types 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →