Delete a database backup configuration
AI agents call delete_database_backup to permanently remove resources in Ploi MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a database backup configuration, which cannot be undone. Even though it targets a backup rather than the live database, deletion of backups is irreversible and eliminates recovery options. This warrants the Destructive category.
From the tool's definition Tool name is 'delete_database_backup' and description states 'Delete a database backup configuration'. The verb 'delete' combined with the target 'database backup' indicates irreversible removal of data or configuration.
Attacks that exploit this kind of access
Delete a database backup configuration. It is categorised as a Destructive tool in the Ploi MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ploi MCP Server MCP server in PolicyLayer and add a rule for delete_database_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 Ploi MCP Server. Nothing to install.
delete_database_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 delete_database_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 delete_database_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.
delete_database_backup is provided by the Ploi MCP Server MCP server (sudanese/ploi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →