create_namespace · K8s MCP: Risk & Policy

WHAT IT DOES

What create_namespace does on K8s MCP

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

WHY IT NEEDS A POLICY

Why create_namespace needs a policy

This tool creates a new namespace in a Kubernetes cluster, which is a reversible write operation. Namespaces are organizational units that can be deleted, making this a Write rather than Destructive action. While namespace creation has organizational consequences, the severity is medium because it doesn't directly compromise running workloads, expose sensitive data, or delete resources.

From the tool's definition Tool name: 'create_namespace'; description: 'Create a new namespace.' The verb 'Create' indicates a write operation that adds a new Kubernetes namespace resource.

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 K8s MCP, 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 K8s MCP 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 K8s 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 K8s MCP. 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 K8s MCP server (rahul007-bit/k8s-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.