Perform comprehensive cluster health check
AI agents call cluster_health_check to retrieve information from Kubernetes MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool gathers and analyzes cluster metrics and status without creating, modifying, deleting, or executing arbitrary operations. It is similar to a health monitoring endpoint that queries cluster state. While it might trigger alerts or notifications based on findings, the tool itself does not perform destructive, write, or execute actions.
From the tool's definition The tool 'cluster_health_check' performs a 'comprehensive cluster health check' which is fundamentally a diagnostic and observability operation. It reads cluster state information without modifying anything.
Attacks that exploit this kind of access
Perform comprehensive cluster health check. It is categorised as a Read tool in the Kubernetes MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for cluster_health_check: 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.
cluster_health_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cluster_health_check 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.
Set action: deny in the PolicyLayer policy for cluster_health_check. 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.
cluster_health_check is provided by the Kubernetes MCP Server MCP server (vivekbala/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →