create_pod · Kube MCP: Risk & Policy

WHAT IT DOES

What create_pod does on Kube

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

WHY IT NEEDS A POLICY

Why create_pod needs a policy

The name 'create_pod' strongly implies creating a new Kubernetes pod, which is a Write operation. However, since the description is empty, confidence is reduced. Creating pods can have high blast radius as it can consume cluster resources, run arbitrary container images, and potentially be used to escalate privileges or exfiltrate data depending on the pod spec allowed.

From the tool's definition Tool name 'create_pod' on a Kubernetes MCP server that manages Kubernetes resources. Description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_pod Rate-limited

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

FAQ

Questions about create_pod

What does the create_pod tool do? +

create_pod. It is categorised as a Write tool in the Kube MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_pod? +

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

What risk level is create_pod? +

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

Can I rate-limit create_pod? +

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

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

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