Manage Kubernetes namespaces: list, create, delete, describe.
AI agents call k8s_namespaces to permanently remove resources in RedisNexus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly supports 'delete' of Kubernetes namespaces, which is an irreversible destructive action. Deleting a namespace in Kubernetes removes all resources within it (pods, services, deployments, secrets, etc.), making this highly impactful. Per severity rules, Destructive takes precedence over Write (create) and Read (list, describe).
From the tool's definition Manage Kubernetes namespaces: list, create, delete, describe.
Attacks that exploit this kind of access
Manage Kubernetes namespaces: list, create, delete, describe. It is categorised as a Destructive tool in the RedisNexus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RedisNexus MCP server in PolicyLayer and add a rule for k8s_namespaces: 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 RedisNexus. Nothing to install.
k8s_namespaces 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_namespaces 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_namespaces. 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_namespaces is provided by the RedisNexus MCP server (rajkumar-madhu/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 →