cpu_get_high_cpu_processes
Get list of processes with high CPU usage.
This record as markdown: /tools/aapanel-mcp/cpu-get-high-cpu-processes.md
What cpu_get_high_cpu_processes does on Aapanel
AI agents call cpu_get_high_cpu_processes 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 cpu_get_high_cpu_processes is rated Low
This tool performs a read-only query of system process information. It retrieves CPU usage metrics and returns a list, with no side effects, no data modification, and no code execution triggered by the query itself. It belongs in the Read category. The severity is low because retrieving process information is informational only and poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name and description indicate a retrieval operation: 'Get list of processes with high CPU usage' — queries system state without modification.
Attacks that exploit this kind of access
The rule that runs cpu_get_high_cpu_processes 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 cpu_get_high_cpu_processes, this is the rule to start with:
cpu_get_high_cpu_processes 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 cpu_get_high_cpu_processes call is checked against it from then on.
Questions about cpu_get_high_cpu_processes
Get list of processes with high CPU usage. 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 cpu_get_high_cpu_processes: 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.
cpu_get_high_cpu_processes 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 cpu_get_high_cpu_processes 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 cpu_get_high_cpu_processes. 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.
cpu_get_high_cpu_processes 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