create-namespace · Kubernetes MCP Server MCP: Risk & Policy

WHAT IT DOES

What create-namespace does on Kubernetes MCP Server

AI agents use create-namespace to create or update resources in Kubernetes MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kubernetes MCP Server environment.

WHY IT NEEDS A POLICY

Why create-namespace needs a policy

Creating a namespace in Kubernetes is a write operation that adds a new resource to the cluster. While it is reversible (unlike destructive operations), it modifies cluster state and could affect workload isolation and resource organization.

From the tool's definition Tool is named 'create-namespace' and described as 'Create a new namespace', which creates a new Kubernetes namespace resource. This is a reversible create operation (namespaces can be deleted).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create-namespace Rate-limited

create-namespace stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create-namespace": {
      "limits": [
        {
          "counter": "create-namespace_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kubernetes MCP Server, so you can run agents against it safely.

FAQ

Questions about create-namespace

What does the create-namespace tool do? +

Create a new namespace. It is categorised as a Write tool in the Kubernetes MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create-namespace? +

Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for create-namespace: 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.

What risk level is create-namespace? +

create-namespace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create-namespace? +

Yes. Add a rate_limit block to the create-namespace 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 create-namespace completely? +

Set action: deny in the PolicyLayer policy for create-namespace. 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 create-namespace? +

create-namespace 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.