// SCAN REPORT

Kubernetes MCP

3 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 5 Jul 2026

1 can modify or destroy data

2 read-only

3 tools total

Community server · catalogue entry verified 05/07/2026

How to control Kubernetes MCP ↓

TOOL MAP

What Kubernetes MCP exposes to your agents

Read (2) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Kubernetes MCP tools

Write · High patch_resource The patch_resource tool modifies Kubernetes resources, which falls squarely into the Write category.

1 of Kubernetes MCP's 3 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Kubernetes MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Kubernetes MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "patch_resource": {
    "limits": [
      {
        "counter": "patch_resource_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_resource": {
    "limits": [
      {
        "counter": "get_resource_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Kubernetes MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON KUBERNETES →

Instant setup, no code required.

FULL CATALOGUE

All 3 Kubernetes MCP tools

WRITE 1 tools

Write patch_resource patch_resource

READ 2 tools

Read get_resource get_resource Read get_resources get_resources

FAQ

Questions about Kubernetes MCP

How do I prevent bulk modifications through Kubernetes MCP? +

The Kubernetes MCP server has 1 write tools including patch_resource. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Kubernetes MCP.

How many tools does the Kubernetes MCP server expose? +

3 tools across 2 categories: Read, Write. 2 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Kubernetes MCP? +

Register the Kubernetes MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Kubernetes MCP tool call.

Deterministic rules across all 3 Kubernetes MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON KUBERNETES →

Instant setup, no code required.

3 Kubernetes MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.