k8s_exec_pod · Kubernetes MCP Server MCP: Risk & Policy

WHAT IT DOES

What k8s_exec_pod does on Kubernetes MCP Server

AI agents invoke k8s_exec_pod 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 k8s_exec_pod needs a policy

This tool allows arbitrary command execution within Kubernetes pods, which can have wide-ranging effects depending on what commands are run. An AI agent with access to this tool could modify application state, exfiltrate data, pivot to other systems, or compromise workloads.

From the tool's definition Tool executes arbitrary commands in pod containers via 'Execute a command in a pod container'. Similar to shell command execution, this enables running code with the privileges and context of the target pod.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

k8s_exec_pod Rate-limited

k8s_exec_pod 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": {
    "k8s_exec_pod": {
      "limits": [
        {
          "counter": "k8s_exec_pod_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 k8s_exec_pod

What does the k8s_exec_pod tool do? +

Execute a command in a pod container. 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 k8s_exec_pod? +

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

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

Can I rate-limit k8s_exec_pod? +

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

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

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