get_node_health

Node readiness and pressure conditions for all nodes

Server Kubernetes + Prometheus SRE MCP Server manishmaurya22/sre-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_node_health does on Kubernetes + Prometheus SRE MCP Server

AI agents call get_node_health to retrieve information from Kubernetes + Prometheus SRE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_node_health needs a policy

This tool retrieves diagnostic information about Kubernetes node health status. It performs no modifications, deletions, or external operations—it only queries and returns existing cluster state. No side effects or resource changes occur from invoking this tool. It falls clearly into the Read category with low severity since misuse would only surface cluster state information without enabling cluster compromise.

From the tool's definition Tool name 'get_node_health' and description 'Node readiness and pressure conditions for all nodes' indicate a retrieval operation that queries cluster state without modification.

Questions about get_node_health

What does the get_node_health tool do? +

Node readiness and pressure conditions for all nodes. It is categorised as a Read tool in the Kubernetes + Prometheus SRE MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_node_health? +

Register the Kubernetes + Prometheus SRE MCP Server MCP server in PolicyLayer and add a rule for get_node_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 Kubernetes + Prometheus SRE MCP Server. Nothing to install.

What risk level is get_node_health? +

get_node_health is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_node_health? +

Yes. Add a rate_limit block to the get_node_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.

How do I block get_node_health completely? +

Set action: deny in the PolicyLayer policy for get_node_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.

What MCP server provides get_node_health? +

get_node_health is provided by the Kubernetes + Prometheus SRE MCP Server MCP server (manishmaurya22/sre-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.