list_kernels
Get a list of all available kernels
This record as markdown: /tools/takashito-linode-mcp-server/list-kernels.md
What list_kernels does on Linode MCP Server
AI agents call list_kernels 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.
Why list_kernels is rated Low
This tool performs a simple query to enumerate available kernels, which is a non-destructive, informational operation. It has no ability to modify state, execute code, delete resources, or affect financial systems. The blast radius of misuse is minimal.
From the tool's definition Tool name 'list_kernels' and description 'Get a list of all available kernels' indicate a read-only operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_kernels 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_kernels, this is the rule to start with:
list_kernels is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every list_kernels call is checked against it from then on.
Questions about list_kernels
Get a list of all available kernels. 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_kernels: 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_kernels 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_kernels 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_kernels. 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_kernels 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.
More on Linode MCP Server, and thousands of servers like it.
This server
Across the catalogue