Get current CPU load and average information
AI agents call get_cpu_load to retrieve information from System Information MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries CPU load statistics from the host system. It is a passive read-only operation that returns monitoring data without side effects, state changes, or the ability to trigger external operations. It poses minimal risk if misused by an AI agent, as the worst case is reading stale or unnecessary metrics.
From the tool's definition Tool name and description: 'Get current CPU load and average information' — purely retrieves system metrics with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get current CPU load and average information. It is categorised as a Read tool in the System Information MCP Server MCP Server, which means it retrieves data without modifying state.
Register the System Information MCP Server MCP server in PolicyLayer and add a rule for get_cpu_load: 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 System Information MCP Server. Nothing to install.
get_cpu_load 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_load 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_load. 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_load is provided by the System Information MCP Server MCP server (markolive1501/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 →