Permanently delete a WordPress plugin from the filesystem. The plugin must be deactivated first. This cannot be undone.
AI agents call wp_plugin_delete to permanently remove resources in Wp Cli — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes plugin files from disk with no recovery mechanism. An AI agent given this tool could delete critical plugins, break site functionality, or remove security-related plugins. The irreversibility and potential for cascading damage to site operations warrant critical severity. The explicit 'cannot be undone' language confirms destructive rather than write classification.
From the tool's definition "Permanently delete a WordPress plugin from the filesystem" and "This cannot be undone." The tool explicitly performs irreversible deletion of plugin files.
Attacks that exploit this kind of access
Permanently delete a WordPress plugin from the filesystem. The plugin must be deactivated first. This cannot be undone. It is categorised as a Destructive tool in the Wp Cli MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Wp Cli MCP server in PolicyLayer and add a rule for wp_plugin_delete: 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 Wp Cli. Nothing to install.
wp_plugin_delete 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 wp_plugin_delete 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 wp_plugin_delete. 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.
wp_plugin_delete is provided by the Wp Cli MCP server (mvtandas/wp-cli-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 →