select_kube_context · Kube Lint MCP: Risk & Policy

WHAT IT DOES

What select_kube_context does on Kube Lint

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

WHY IT NEEDS A POLICY

Why select_kube_context needs a policy

This tool modifies the active Kubernetes context configuration, affecting all subsequent operations. It writes/updates the current context state rather than just reading it. Misuse could redirect all subsequent kubectl/API calls to an unintended cluster, but it doesn't directly destroy data or move money.

From the tool's definition "Select the Kubernetes context for all subsequent operations"

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

select_kube_context Rate-limited

select_kube_context 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": {
    "select_kube_context": {
      "limits": [
        {
          "counter": "select_kube_context_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 Lint, so you can run agents against it safely.

FAQ

Questions about select_kube_context

What does the select_kube_context tool do? +

Select the Kubernetes context for all subsequent operations.\n. It is categorised as a Write tool in the Kube Lint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on select_kube_context? +

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

What risk level is select_kube_context? +

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

Can I rate-limit select_kube_context? +

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

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

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