use-context · Kubernetes MCP Server MCP: Risk & Policy

WHAT IT DOES

What use-context does on Kubernetes MCP Server

AI agents invoke use-context to trigger actions in Kubernetes MCP Server. 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 use-context needs a policy

Switching kubectl context changes which Kubernetes cluster all subsequent operations target. This is an Execute-level action because it triggers an external configuration change that affects the scope of all future cluster operations. Misuse could cause an AI agent to inadvertently operate on production clusters instead of dev/test environments, with potentially high blast radius.

From the tool's definition Switch to a different kubectl context

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

use-context Rate-limited

use-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": {
    "use-context": {
      "limits": [
        {
          "counter": "use-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 Kubernetes MCP Server, so you can run agents against it safely.

FAQ

Questions about use-context

What does the use-context tool do? +

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

How do I enforce a policy on use-context? +

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

What risk level is use-context? +

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

Can I rate-limit use-context? +

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

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

use-context 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.