query_cluster_node_usage

query_cluster_node_usage

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

What query_cluster_node_usage does on OpenShift OVN-Kubernetes Benchmark MCP Server

AI agents call query_cluster_node_usage 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 query_cluster_node_usage needs a policy

The tool name and context suggest it retrieves cluster node usage metrics without modification. However, the empty description and potential for querying sensitive operational data in an OpenShift environment warrant medium severity due to information disclosure risk. Confidence is moderate because the actual scope and access controls are unknown.

From the tool's definition Tool name 'query_cluster_node_usage' indicates data retrieval (query pattern). Sibling tools on this server follow Read patterns (get_*, query_*). No description provided to confirm scope.

Questions about query_cluster_node_usage

What does the query_cluster_node_usage tool do? +

query_cluster_node_usage. 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 query_cluster_node_usage? +

Register the OpenShift OVN-Kubernetes Benchmark MCP Server MCP server in PolicyLayer and add a rule for query_cluster_node_usage: 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 query_cluster_node_usage? +

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

Can I rate-limit query_cluster_node_usage? +

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

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

query_cluster_node_usage 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.

// THE FULL RECORD

query_cluster_node_usage is one line of OpenShift OVN-Kubernetes Benchmark MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.