get_mcp_health_status

Return health status for MCP server, Prometheus, and KubeAPI with improved error handling

Server OpenShift OVN-Kubernetes Benchmark MCP Server liqcui/ovnk-benchmark-mcp
Category Read
Risk class Low
Parameters 00 required

What get_mcp_health_status does on OpenShift OVN-Kubernetes Benchmark MCP Server

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

Why get_mcp_health_status needs a policy

This tool performs a straightforward status check and monitoring query. It retrieves health information without modifying any state, triggering external operations, or deleting data. This is a classic Read operation—monitoring and observability data retrieval. The blast radius of misuse is minimal since the tool only returns status information and does not affect cluster state or performance.

From the tool's definition Tool name 'get_mcp_health_status' and description 'Return health status' indicate a query/retrieval operation that checks the status of MCP server, Prometheus, and KubeAPI.

Questions about get_mcp_health_status

What does the get_mcp_health_status tool do? +

Return health status for MCP server, Prometheus, and KubeAPI with improved error handling. It is categorised as a Read tool in the OpenShift OVN-Kubernetes Benchmark MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_mcp_health_status? +

Register the OpenShift OVN-Kubernetes Benchmark MCP Server MCP server in PolicyLayer and add a rule for get_mcp_health_status: 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 OpenShift OVN-Kubernetes Benchmark MCP Server. Nothing to install.

What risk level is get_mcp_health_status? +

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

Can I rate-limit get_mcp_health_status? +

Yes. Add a rate_limit block to the get_mcp_health_status 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_mcp_health_status completely? +

Set action: deny in the PolicyLayer policy for get_mcp_health_status. 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_mcp_health_status? +

get_mcp_health_status is provided by the OpenShift OVN-Kubernetes Benchmark MCP Server MCP server (liqcui/ovnk-benchmark-mcp). 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.