switch_context · kube- MCP: Risk & Policy

WHAT IT DOES

What switch_context does on kube-MCP

AI agents invoke switch_context to trigger actions in kube-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why switch_context needs a policy

Switching Kubernetes context changes the active cluster/namespace target for all subsequent operations. This is not a simple read or write — it triggers an operational state change that affects which cluster all future commands are executed against. Misuse could cause an AI agent to inadvertently target a production cluster instead of a dev cluster, leading to high-blast-radius consequences.

From the tool's definition Switch Kubernetes context

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

switch_context Rate-limited

switch_context stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "switch_context": {
      "limits": [
        {
          "counter": "switch_context_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 switch_context

What does the switch_context tool do? +

Switch Kubernetes context. It is categorised as a Execute tool in the kube-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on switch_context? +

Register the kube- MCP server in PolicyLayer and add a rule for switch_context: 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 switch_context? +

switch_context is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit switch_context? +

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

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

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