get_ocp_node_runtime_errors
AI agents call get_ocp_node_runtime_errors 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.
Based on naming convention and the 'get_' prefix pattern consistent with sibling tools (get_api_server_stats, get_egressip_status, get_etcd_cluster_status, etc.), this tool retrieves runtime error information from OCP nodes without modifying state. No write, execute, destructive, or financial operations are implied.
From the tool's definition Tool name 'get_ocp_node_runtime_errors' uses the 'get_' prefix which conventionally indicates data retrieval. The verb 'get' is a passive read operation. Tool description is empty, limiting specificity.
Attacks that exploit this kind of access
get_ocp_node_runtime_errors. 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_ocp_node_runtime_errors: 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_ocp_node_runtime_errors 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_ocp_node_runtime_errors 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_ocp_node_runtime_errors. 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_ocp_node_runtime_errors 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 →