// SCAN REPORT

Kubernetes Monitor

12 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 12 Jun 2026

0 can modify or destroy data

12 read-only

12 tools total

Community server · catalogue entry verified 12/06/2026

How to control Kubernetes Monitor ↓

TOOL MAP

What Kubernetes Monitor exposes to your agents

Read (12) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Kubernetes Monitor

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

Cap read operations

{
  "high_restart_pods": {
    "limits": [
      {
        "counter": "high_restart_pods_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 Monitor — 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 MONITOR →

Free to start. No card required.

FULL CATALOGUE

All 12 Kubernetes Monitor tools

READ 12 tools

Read high_restart_pods Find pods with high restart counts (>5) Read failed_pods failed_pods Read get_namespaces get_namespaces Read get_resource_yaml get_resource_yaml Read list_deployments List deployments with optional namespace filter Read list_events List events with optional namespace filter Read list_nodes List all nodes and their status Read list_pods list_pods Read list_services List services with optional namespace filter Read node_capacity node_capacity Read orphaned_resources List resources that might be orphaned (no owner references) Read pending_pods List all pods in Pending state and why they're pending

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Kubernetes Monitor

Is the Kubernetes Monitor MCP server safe to use without restrictions? +

The Kubernetes Monitor server is primarily read-only with 12 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Kubernetes Monitor MCP server expose? +

12 tools across 2 categories: Execute, Read. 12 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Kubernetes Monitor? +

Register the Kubernetes Monitor 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 Monitor tool call.

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

ENFORCE POLICY ON KUBERNETES MONITOR →

Free to start. No card required.

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