get_network_io_node
AI agents call get_network_io_node 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.
Despite the empty description, the naming convention and peer tools strongly suggest this retrieves performance/monitoring data about network I/O on a node. This is a query/retrieval operation with no side effects, placing it in the Read category. Confidence is lowered slightly (0.75 instead of higher) due to the absence of an explicit description, though context provides reasonable justification.
From the tool's definition Tool name 'get_network_io_node' indicates retrieval of network I/O metrics for a node. The prefix 'get_' and context of sibling 'Read' tools (get_api_server_stats, get_egressip_status, get_etcd_cluster_status, get_etcd_general_info) consistently indicate data…
Attacks that exploit this kind of access
get_network_io_node. 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_network_io_node: 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_network_io_node 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_network_io_node 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_network_io_node. 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_network_io_node 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 →