pod_exec · kube- MCP: Risk & Policy

WHAT IT DOES

What pod_exec does on kube-MCP

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

This tool allows running arbitrary code/commands inside a containerized environment, which is a classic Execute category action. The blast radius is high because pod_exec could be used to compromise the pod, exfiltrate data, modify running processes, or pivot to other cluster resources depending on the pod's permissions and network access.

From the tool's definition Tool name 'pod_exec' and description 'Execute a command in a pod' directly indicate execution of arbitrary commands within a Kubernetes pod environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pod_exec Rate-limited

pod_exec 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": {
    "pod_exec": {
      "limits": [
        {
          "counter": "pod_exec_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 pod_exec

What does the pod_exec tool do? +

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

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

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

Can I rate-limit pod_exec? +

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

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

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

// THE FULL RECORD

pod_exec is one line of kube-'s registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →