list_kubernetes_tier_versions
List available Kubernetes versions for a specific tier
This record as markdown: /tools/takashito-linode-mcp-server/list-kubernetes-tier-versions.md
What list_kubernetes_tier_versions does on Linode MCP Server
AI agents call list_kubernetes_tier_versions 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_kubernetes_tier_versions is rated Low
This tool retrieves and displays available Kubernetes version information for a given tier. It performs no modifications, deletions, executions, or financial operations. It is a simple informational query with no side effects, making it a Read category risk with low severity. An AI agent cannot cause meaningful harm by calling this tool, as it only exposes existing system information.
From the tool's definition Tool name 'list_kubernetes_tier_versions' and description 'List available Kubernetes versions for a specific tier' indicate retrieval of metadata without modification. The verb 'list' is a classic read operation that queries available versions.
Attacks that exploit this kind of access
The rule that runs list_kubernetes_tier_versions 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_kubernetes_tier_versions, this is the rule to start with:
list_kubernetes_tier_versions 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_kubernetes_tier_versions call is checked against it from then on.
Questions about list_kubernetes_tier_versions
List available Kubernetes versions for a specific tier. 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_kubernetes_tier_versions: 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_kubernetes_tier_versions 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_kubernetes_tier_versions 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_kubernetes_tier_versions. 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_kubernetes_tier_versions 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