// MCP TOOL REFERENCE

KUBERNETES MONITOR TOOLS

12 tools from the Kubernetes Monitor MCP Server, categorised by risk level.

// 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

// FAQ

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

The Kubernetes Monitor MCP server exposes 12 tools across 1 categories: Read.

How do I enforce policies on Kubernetes Monitor tools? +

Route the Kubernetes Monitor server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Kubernetes Monitor tools fall into? +

Kubernetes Monitor tools are categorised as Read (12). Each category has a recommended default policy.

Enforce policy on every Kubernetes Monitor tool call.

Start from Kubernetes Monitor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.