New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

claudeus_wp_plugins__delete

Delete a plugin. Permanently remove an inactive plugin from the site. Plugin must be deactivated first.

SERVERClaudeus WordPress MCP SOURCEdeus-h/claudeus-wp-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-plugins--delete.md

What claudeus_wp_plugins__delete does on Claudeus WordPress MCP

AI agents call claudeus_wp_plugins__delete to permanently remove resources in Claudeus WordPress MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why claudeus_wp_plugins__delete is rated Critical

This tool irreversibly deletes a plugin from a WordPress installation. Once deleted, the plugin code and data are removed and cannot be undone without restoration from backups. This is a classic destructive operation with no rollback capability. While the tool requires prior deactivation as a safeguard, deletion itself remains a permanent action.

From the tool's definition Tool name contains 'delete' and description states 'Permanently remove an inactive plugin from the site.' The word 'permanently' and 'delete' are explicit indicators of irreversible data destruction.

Questions about claudeus_wp_plugins__delete

What does the claudeus_wp_plugins__delete tool do? +

Delete a plugin. Permanently remove an inactive plugin from the site. Plugin must be deactivated first. It is categorised as a Destructive tool in the Claudeus WordPress MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on claudeus_wp_plugins__delete? +

Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_plugins__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 Claudeus WordPress MCP. Nothing to install.

What risk level is claudeus_wp_plugins__delete? +

claudeus_wp_plugins__delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit claudeus_wp_plugins__delete? +

Yes. Add a rate_limit block to the claudeus_wp_plugins__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.

How do I block claudeus_wp_plugins__delete completely? +

Set action: deny in the PolicyLayer policy for claudeus_wp_plugins__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.

What MCP server provides claudeus_wp_plugins__delete? +

claudeus_wp_plugins__delete is provided by the Claudeus WordPress MCP server (deus-h/claudeus-wp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Claudeus WordPress, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claudeus WordPress's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.