get_etcd_cluster_status
AI agents call get_etcd_cluster_status to retrieve information from OCP Performance Analyzer MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves cluster status information from etcd in an OpenShift/Kubernetes monitoring context. This is a read operation that queries existing state without modification, deletion, or execution of arbitrary code. No side effects or destructive capabilities are indicated. Severity is low because status queries have minimal blast radius even if misused by an agent.
From the tool's definition Tool name 'get_etcd_cluster_status' indicates a status retrieval operation. The 'get_' prefix is a standard convention for read-only queries.
Attacks that exploit this kind of access
get_etcd_cluster_status. It is categorised as a Read tool in the OCP Performance Analyzer MCP MCP Server, which means it retrieves data without modifying state.
Register the OCP Performance Analyzer MCP server in PolicyLayer and add a rule for get_etcd_cluster_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 OCP Performance Analyzer MCP. Nothing to install.
get_etcd_cluster_status 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_etcd_cluster_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.
Set action: deny in the PolicyLayer policy for get_etcd_cluster_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.
get_etcd_cluster_status is provided by the OCP Performance Analyzer MCP server (openshift-eng/ocp-performance-analyzer-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 →