This record as markdown: /tools/aapanel-mcp/database-get-slow-log.md
What database_get_slow_log does on Aapanel
AI agents call database_get_slow_log 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 database_get_slow_log is rated Low
This tool retrieves and queries existing MySQL slow query log data for diagnostic purposes. It has no side effects, does not modify data, execute code, or delete anything. It is purely informational, similar to viewing logs or running SELECT queries. The blast radius of misuse is minimal—an attacker gains visibility into slow queries but cannot alter system state or cause damage.
From the tool's definition Tool name 'database_get_slow_log' and description 'Get MySQL slow query log' indicate retrieval of log data with no modification or execution of commands. The verb 'Get' is explicitly a read operation.
Attacks that exploit this kind of access
The rule that runs database_get_slow_log 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 database_get_slow_log, this is the rule to start with:
database_get_slow_log 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 database_get_slow_log call is checked against it from then on.
Questions about database_get_slow_log
Get MySQL slow query log. 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 database_get_slow_log: 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.
database_get_slow_log 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 database_get_slow_log 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 database_get_slow_log. 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.
database_get_slow_log 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