Get CPU information and load averages.
AI agents call get_cpu_info to retrieve information from Linux MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns CPU metrics (information and load averages) without performing any side effects, modifications, or state changes. It is a straightforward read operation on system diagnostics data. The server is explicitly documented as read-only, and this tool fits that constraint perfectly.
From the tool's definition Tool name 'get_cpu_info' and server description explicitly stating 'read-only Linux system diagnostics.' The function retrieves CPU information and load averages with no modification, creation, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get CPU information and load averages. It is categorised as a Read tool in the Linux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linux MCP Server 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 Linux MCP Server. 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 Linux MCP Server MCP server (narmaku/linux-mcp-server-archived). 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 →