AI agents use create_kubernetes_cluster to create or update resources in Linode MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linode MCP Server environment.
This tool creates a new Kubernetes cluster, which is a significant Write operation. It provisions cloud infrastructure resources (compute, networking, etc.) that incur costs and require explicit teardown, but it is technically reversible (clusters can be deleted). Severity is high because misconfiguration or unintended creation can spin up expensive infrastructure and expose attack surfaces.
From the tool's definition Create a new Kubernetes cluster
Documented attack patterns abuse exactly the kind of access create_kubernetes_cluster gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_kubernetes_cluster:
{
"version": "1",
"default": "deny",
"tools": {
"create_kubernetes_cluster": {
"limits": [
{
"counter": "create_kubernetes_cluster_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_kubernetes_cluster stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new Kubernetes cluster. It is categorised as a Write tool in the Linode MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for create_kubernetes_cluster: 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.
create_kubernetes_cluster is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_kubernetes_cluster 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 create_kubernetes_cluster. 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.
create_kubernetes_cluster 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.
Start from Linode MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
416 Linode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.