regenerate_kubernetes_cluster

Regenerate a Kubernetes cluster

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/takashito-linode-mcp-server/regenerate-kubernetes-cluster.md

WHAT IT DOES

What regenerate_kubernetes_cluster does on Linode MCP Server

AI agents call regenerate_kubernetes_cluster to permanently remove resources in Linode MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why regenerate_kubernetes_cluster is rated Critical

Regenerating a Kubernetes cluster typically involves tearing down and recreating the cluster infrastructure, which is an irreversible destructive operation. All running workloads, persistent data (unless externally backed up), and cluster configurations would be lost. The blast radius is critical as this affects an entire Kubernetes cluster and all workloads running on it.

From the tool's definition 'Regenerate a Kubernetes cluster' — regenerating a cluster implies destroying and recreating it, which would irreversibly delete existing cluster state, workloads, and configurations

Attacks that exploit this kind of access

RECOMMENDED RULE

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

regenerate_kubernetes_cluster Hidden

regenerate_kubernetes_cluster is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "regenerate_kubernetes_cluster"
  ]
}

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

FAQ

Questions about regenerate_kubernetes_cluster

What does the regenerate_kubernetes_cluster tool do? +

Regenerate a Kubernetes cluster. It is categorised as a Destructive tool in the Linode MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on regenerate_kubernetes_cluster? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for regenerate_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.

What risk level is regenerate_kubernetes_cluster? +

regenerate_kubernetes_cluster is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit regenerate_kubernetes_cluster? +

Yes. Add a rate_limit block to the regenerate_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.

How do I block regenerate_kubernetes_cluster completely? +

Set action: deny in the PolicyLayer policy for regenerate_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.

What MCP server provides regenerate_kubernetes_cluster? +

regenerate_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.

KEEP EXPLORING

More on Linode MCP Server, and thousands of servers like it.

This server

All 416 Linode MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →