abnormal_check_cpu
Check overall CPU for abnormal usage patterns.
This record as markdown: /tools/aapanel-mcp/abnormal-check-cpu.md
What abnormal_check_cpu does on Aapanel
AI agents call abnormal_check_cpu to retrieve information from Aapanel without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why abnormal_check_cpu is rated Low
This tool queries CPU status to detect anomalies but performs no mutations, executions, or resource-consuming operations. It is a read-only diagnostic check typical of system monitoring. Severity is low because misuse would only result in information disclosure of CPU metrics, not system compromise or data loss.
From the tool's definition Tool name 'abnormal_check_cpu' and description 'Check overall CPU for abnormal usage patterns' indicate a monitoring/diagnostic operation that retrieves system metrics without modification.
Attacks that exploit this kind of access
The rule that runs abnormal_check_cpu safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For abnormal_check_cpu, this is the rule to start with:
abnormal_check_cpu is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every abnormal_check_cpu call is checked against it from then on.
Questions about abnormal_check_cpu
Check overall CPU for abnormal usage patterns. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.
Register the Aapanel MCP server in PolicyLayer and add a rule for abnormal_check_cpu: 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 Aapanel. Nothing to install.
abnormal_check_cpu 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 abnormal_check_cpu 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 abnormal_check_cpu. 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.
abnormal_check_cpu is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
This server
Across the catalogue