Deletes managed backup artifacts for the selected LocalWP site based on age and/or retention. Requires the
AI agents call cleanup_backups to permanently remove resources in LocalWP MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes backup artifacts, which is an irreversible destructive action. Backup data, once deleted, cannot be recovered, making misuse particularly dangerous as it could eliminate the only recovery points for a WordPress site. The blast radius is high because losing backups means losing the ability to recover from other failures.
From the tool's definition 'Deletes managed backup artifacts' - explicitly removes backup files based on age and/or retention policy, which is irreversible deletion of backup data
Attacks that exploit this kind of access
Deletes managed backup artifacts for the selected LocalWP site based on age and/or retention. Requires the. It is categorised as a Destructive tool in the LocalWP MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LocalWP MCP server in PolicyLayer and add a rule for cleanup_backups: 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 LocalWP MCP. Nothing to install.
cleanup_backups 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 cleanup_backups 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 cleanup_backups. 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.
cleanup_backups is provided by the LocalWP MCP server (kazimshah39/localwp-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 →