This record as markdown: /tools/aapanel-mcp/database-delete-backup.md
What database_delete_backup does on Aapanel
AI agents call database_delete_backup 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 database_delete_backup is rated Critical
This tool permanently removes database backup files, which cannot be recovered once deleted. This is an irreversible destructive action that eliminates data recovery options. While not immediately affecting live production data, it removes critical backups needed for disaster recovery.
From the tool's definition Tool name: 'database_delete_backup'; description: 'Delete a database backup.' The verb 'delete' combined with 'backup' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs database_delete_backup 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_delete_backup, this is the rule to start with:
database_delete_backup 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 database_delete_backup call is checked against it from then on.
Questions about database_delete_backup
Delete a database backup. 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 database_delete_backup: 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_delete_backup 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 database_delete_backup 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_delete_backup. 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_delete_backup 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