get_kubelet_cni_stats
AI agents call get_kubelet_cni_stats 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.
This tool appears to retrieve Container Network Interface statistics from kubelet without modifying any state. While the description is empty, the naming pattern and server context consistently indicate Read-category tools for performance monitoring. The blast radius is minimal as it only queries data.
From the tool's definition Tool name 'get_kubelet_cni_stats' contains 'get', which indicates data retrieval. Context shows this is part of a performance analysis platform with sibling tools like 'get_api_server_stats', 'get_etcd_cluster_status', etc., all of which are clearly Read…
Attacks that exploit this kind of access
get_kubelet_cni_stats. 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_kubelet_cni_stats: 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_kubelet_cni_stats 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_kubelet_cni_stats 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_kubelet_cni_stats. 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_kubelet_cni_stats 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 →