Comprehensive Kubernetes cluster health check. Checks nodes, pods, deployments, resource pressure.
AI agents call k8s_cluster_health to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs monitoring and diagnostic queries of Kubernetes cluster status. It retrieves information about nodes, pods, deployments, and resource metrics but does not create, modify, delete, or execute operations. This is purely observational/read-only telemetry, making it a Read category tool with low severity risk.
From the tool's definition Tool description states 'health check' and 'Checks nodes, pods, deployments, resource pressure' — these are read-only diagnostic operations that query cluster state without modifying or executing anything.
Attacks that exploit this kind of access
Comprehensive Kubernetes cluster health check. Checks nodes, pods, deployments, resource pressure. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for k8s_cluster_health: 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 RedisNexus. Nothing to install.
k8s_cluster_health 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 k8s_cluster_health 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 k8s_cluster_health. 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.
k8s_cluster_health is provided by the RedisNexus MCP server (rajkumar-madhu/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 →