AI agents call get_cpu_info to retrieve information from Mcp Ssh without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns CPU statistics without side effects. It performs a read-only operation on system state, similar to running 'lscpu' or 'top' for information gathering. There is no data modification, deletion, command execution with unpredictable effects, or financial impact. The low severity reflects that CPU information disclosure poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_cpu_info' and description 'Get detailed CPU usage and statistics' indicate retrieval of system information with no modification or execution of commands.
Attacks that exploit this kind of access
Get detailed CPU usage and statistics. It is categorised as a Read tool in the Mcp Ssh MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ssh MCP server in PolicyLayer and add a rule for get_cpu_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 Mcp Ssh. Nothing to install.
get_cpu_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_cpu_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_cpu_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_cpu_info is provided by the Mcp Ssh MCP server (zhouxiangjing/mcp-ssh). 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 →