Get CPU usage statistics.
AI agents call get_cpu_usage to retrieve information from Enterprise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system metrics (CPU usage statistics) for observability purposes. It has no side effects, does not modify state, and does not execute code or commands. It falls squarely into the Read category. The severity is low because reading CPU metrics poses minimal risk even if misused by an agent—at worst it discloses non-sensitive operational telemetry.
From the tool's definition Tool name is 'get_cpu_usage' and description states 'Get CPU usage statistics' — both indicate retrieval of monitoring data with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get CPU usage statistics. It is categorised as a Read tool in the Enterprise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enterprise MCP Server MCP server in PolicyLayer and add a rule for get_cpu_usage: 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 Enterprise MCP Server. Nothing to install.
get_cpu_usage 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_usage 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_usage. 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_usage is provided by the Enterprise MCP Server MCP server (maybeswapnil/enterprise-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_cpu_usage is one line of Enterprise MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →