abnormal_check_mysql_cpu

Check MySQL CPU usage for abnormalities.

SERVERAapanel SOURCEnipunanirmal/aapanel-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aapanel-mcp/abnormal-check-mysql-cpu.md

WHAT IT DOES

What abnormal_check_mysql_cpu does on Aapanel

AI agents call abnormal_check_mysql_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.

RISK

Why abnormal_check_mysql_cpu is rated Low

This tool queries MySQL CPU usage data to detect anomalies. It performs a read-only diagnostic check with no side effects, no data modifications, and no execution of commands. The blast radius of misuse is minimal—an attacker could only gain visibility into MySQL performance metrics, not affect system integrity or availability.

From the tool's definition Tool name contains 'check' and description states 'Check MySQL CPU usage for abnormalities' — purely a monitoring/diagnostic operation that retrieves system metrics without modifying state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs abnormal_check_mysql_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_mysql_cpu, this is the rule to start with:

abnormal_check_mysql_cpu Allowed

abnormal_check_mysql_cpu is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "abnormal_check_mysql_cpu": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every abnormal_check_mysql_cpu call is checked against it from then on.

FAQ

Questions about abnormal_check_mysql_cpu

What does the abnormal_check_mysql_cpu tool do? +

Check MySQL CPU usage for abnormalities. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on abnormal_check_mysql_cpu? +

Register the Aapanel MCP server in PolicyLayer and add a rule for abnormal_check_mysql_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.

What risk level is abnormal_check_mysql_cpu? +

abnormal_check_mysql_cpu is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit abnormal_check_mysql_cpu? +

Yes. Add a rate_limit block to the abnormal_check_mysql_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.

How do I block abnormal_check_mysql_cpu completely? +

Set action: deny in the PolicyLayer policy for abnormal_check_mysql_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.

What MCP server provides abnormal_check_mysql_cpu? +

abnormal_check_mysql_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.

KEEP EXPLORING

More on Aapanel, and thousands of servers like it.

This server

All 282 Aapanel tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →