list_instance_types

Get a list of all available Linode types, including pricing and specifications

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server

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/takashito-linode-mcp-server/list-instance-types.md

WHAT IT DOES

What list_instance_types does on Linode MCP Server

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.

RISK

Why list_instance_types is rated Low

This is a query/list operation that retrieves publicly available configuration and pricing information about Linode's offerings. It does not create, modify, delete, execute commands, or move money. The data retrieved is informational and the operation has no side effects on infrastructure or account state.

From the tool's definition Tool name 'list_instance_types' and description 'Get a list of all available Linode types, including pricing and specifications' indicate a retrieval operation with no side effects. Returns static reference data about available instance types.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_instance_types Allowed

list_instance_types 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_instance_types": {}
  }
}

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

FAQ

Questions about list_instance_types

What does the list_instance_types tool do? +

Get a list of all available Linode types, including pricing and specifications. 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_instance_types? +

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.

What risk level is list_instance_types? +

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

Can I rate-limit list_instance_types? +

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.

How do I block list_instance_types completely? +

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.

What MCP server provides list_instance_types? +

list_instance_types is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). 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 416 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 →