get_openshift_cluster_info
AI agents call get_openshift_cluster_info 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.
The 'get_' prefix strongly suggests a read-only operation that retrieves cluster information without side effects. Given the server's stated purpose of 'benchmarking and performance monitoring' and the pattern of sibling tools which are all read/analyze operations, this tool most likely queries OpenShift cluster metadata or status.
From the tool's definition Tool name 'get_openshift_cluster_info' indicates data retrieval with 'get' prefix. Description is empty, limiting full assessment.
Attacks that exploit this kind of access
get_openshift_cluster_info. 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.
Register the OpenShift OVN-Kubernetes Benchmark MCP Server MCP server in PolicyLayer and add a rule for get_openshift_cluster_info: 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.
get_openshift_cluster_info 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 get_openshift_cluster_info 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 get_openshift_cluster_info. 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.
get_openshift_cluster_info 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.
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 →