set_namespace · kube- MCP: Risk & Policy

WHAT IT DOES

What set_namespace does on kube-MCP

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

WHY IT NEEDS A POLICY

Why set_namespace needs a policy

This tool modifies the current namespace context, which is a state change in the Kubernetes client configuration. While not destructive (reversible), it alters the working context for subsequent operations.

From the tool's definition Tool name 'set_namespace' and description 'Set current namespace' indicate modification of context state rather than retrieval. The verb 'set' is characteristic of Write operations that change configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_namespace Rate-limited

set_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": {
    "set_namespace": {
      "limits": [
        {
          "counter": "set_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 kube-MCP, so you can run agents against it safely.

FAQ

Questions about set_namespace

What does the set_namespace tool do? +

Set current namespace. It is categorised as a Write tool in the kube-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 set_namespace? +

Register the kube- MCP server in PolicyLayer and add a rule for set_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 kube-MCP. Nothing to install.

What risk level is set_namespace? +

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

Can I rate-limit set_namespace? +

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

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

set_namespace is provided by the kube- MCP server (siddjoshi/kube-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.