Uninstall a 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.
Uninstalling a Helm release removes all deployed resources, configurations, and potentially persistent data associated with that release. This action cannot be easily undone without backups and represents a destructive operation with significant blast radius—an errant invocation could remove critical production services.
From the tool's definition Tool name 'helm-uninstall' and description 'Uninstall a Helm release' indicates irreversible removal of deployed applications and associated resources from a Kubernetes cluster.
Attacks that exploit this kind of access
Uninstall a 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 (thekaranpargaie/kube-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 →