This record as markdown: /tools/aapanel-mcp/system-clear-panel-logs.md
What system_clear_panel_logs does on Aapanel
AI agents call system_clear_panel_logs to permanently remove resources in Aapanel, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why system_clear_panel_logs is rated Critical
Clearing logs is a destructive operation that permanently removes data and cannot be undone. While the blast radius is somewhat contained to system logs rather than production data, logs are critical for security auditing, incident investigation, and compliance.
From the tool's definition Tool name 'system_clear_panel_logs' and description 'Clear aaPanel error logs' indicate irreversible deletion of log data.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_clear_panel_logs 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 system_clear_panel_logs, this is the rule to start with:
system_clear_panel_logs is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every system_clear_panel_logs call is checked against it from then on.
Questions about system_clear_panel_logs
Clear aaPanel error logs. It is categorised as a Destructive tool in the Aapanel MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aapanel MCP server in PolicyLayer and add a rule for system_clear_panel_logs: 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.
system_clear_panel_logs is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the system_clear_panel_logs 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 system_clear_panel_logs. 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.
system_clear_panel_logs 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