Delete a secret
AI agents call k8s_delete_secret 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.
Deleting a secret is an irreversible operation that cannot be undone. Secrets in Kubernetes often contain sensitive credentials, API tokens, TLS certificates, and database passwords. An AI agent misusing this tool could permanently remove critical authentication material, breaking application functionality and requiring manual recovery efforts.
From the tool's definition Tool name is 'k8s_delete_secret' with description 'Delete a secret'. The verb 'delete' indicates irreversible removal of Kubernetes secret resources.
Attacks that exploit this kind of access
Delete a secret. 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 k8s_delete_secret: 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.
k8s_delete_secret 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 k8s_delete_secret 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 k8s_delete_secret. 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.
k8s_delete_secret is provided by the Kubernetes MCP Server MCP server (mjrestivo16/mcp-kubernetes). 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 →