k8s_create_namespace · Kubernetes MCP Server MCP

WHAT IT DOES

What k8s_create_namespace does on Kubernetes MCP Server

AI agents use k8s_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 k8s_create_namespace needs a policy

Creating a namespace is a reversible operation that modifies cluster state by adding a new isolated logical partition. It is a Write operation rather than Destructive (namespaces can be removed) or Execute (it does not run arbitrary code).

From the tool's definition Tool name 'k8s_create_namespace' and description 'Create a new namespace' indicate resource creation. Kubernetes namespaces are logical isolation boundaries but are not destructive (can be deleted) and do not directly modify existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

k8s_create_namespace Rate-limited

k8s_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": {
    "k8s_create_namespace": {
      "limits": [
        {
          "counter": "k8s_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 k8s_create_namespace

What does the k8s_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 k8s_create_namespace? +

Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for k8s_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 k8s_create_namespace? +

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

Can I rate-limit k8s_create_namespace? +

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

Set action: deny in the PolicyLayer policy for k8s_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 k8s_create_namespace? +

k8s_create_namespace 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.