abnormal_check_all
Run all abnormal detection checks at once (MySQL, PHP, CPU, memory, disk).
This record as markdown: /tools/aapanel-mcp/abnormal-check-all.md
What abnormal_check_all does on Aapanel
AI agents invoke abnormal_check_all to trigger actions in Aapanel. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why abnormal_check_all is rated High
This tool actively runs/executes multiple detection checks across system components. While it is primarily read/diagnostic in nature, it 'runs' active checks (not just passive queries), potentially triggering monitoring processes. The blast radius is medium since misuse could cause performance overhead by triggering multiple simultaneous checks, but it does not modify or delete data.
From the tool's definition Run all abnormal detection checks at once (MySQL, PHP, CPU, memory, disk)
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs abnormal_check_all 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_all, this is the rule to start with:
abnormal_check_all stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_all call is checked against it from then on.
Questions about abnormal_check_all
Run all abnormal detection checks at once (MySQL, PHP, CPU, memory, disk). It is categorised as a Execute tool in the Aapanel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aapanel MCP server in PolicyLayer and add a rule for abnormal_check_all: 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_all is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the abnormal_check_all 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_all. 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_all 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.
Across the catalogue