debug-pod · Kubernetes MCP Server MCP: Risk & Policy

WHAT IT DOES

What debug-pod does on Kubernetes MCP Server

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

This tool spawns a new debug container inside an existing pod, which executes a new process/container in the cluster. This is an Execute-category action with high severity because a misused debug container could be used to inspect secrets, access the pod's network namespace, run arbitrary commands inside the cluster, and potentially pivot to other resources.

From the tool's definition Create a debug container in a pod

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debug-pod Rate-limited

debug-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": {
    "debug-pod": {
      "limits": [
        {
          "counter": "debug-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 debug-pod

What does the debug-pod tool do? +

Create a debug container in a pod. 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 debug-pod? +

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

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

Can I rate-limit debug-pod? +

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

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

debug-pod 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.