卸载Helm Release
AI agents call helm_uninstall to permanently remove resources in Kubernetes MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Helm uninstall is a destructive operation that cannot be undone without manual recovery or restoring from backups. It permanently removes deployed applications and their resources from the cluster. This is more severe than Write (reversible modifications) or Execute (code runs with deterministic effects).
From the tool's definition Tool name 'helm_uninstall' with description '卸载Helm Release' (Chinese: 'uninstall Helm Release'). Helm uninstall irreversibly removes a release from the Kubernetes cluster, deleting all associated resources and their configurations.
Attacks that exploit this kind of access
卸载Helm Release. It is categorised as a Destructive tool in the Kubernetes MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for helm_uninstall: 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 Kubernetes MCP Server. Nothing to install.
helm_uninstall is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the helm_uninstall 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 helm_uninstall. 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.
helm_uninstall is provided by the Kubernetes MCP Server MCP server (secret-deus/kubernetes-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →