wordpress_delete_plugin

THE RISK

Critical Risk

Deleting a plugin is an irreversible destructive action that removes code and potentially disables functionality. While the description is uninformative, the unambiguous 'delete' verb in the name, context of a WordPress management server, and comparison to sibling tools like wordpress_bulk_delete_media establish high confidence.

From the tool's definition Tool name 'wordpress_delete_plugin' combined with sibling destructive operations (wordpress_backup_database, wordpress_backup_files, wordpress_bulk_delete_media) and server context describing '190+ tools for content management...and complete site control'.

Documented attack patterns abuse exactly the kind of access wordpress_delete_plugin gives an agent:

HOW TO CONTROL WORDPRESS_DELETE_PLUGIN

PolicyLayer is an MCP gateway — it sits between your AI agents and WordPress MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wordpress_delete_plugin:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "wordpress_delete_plugin"
  ]
}

wordpress_delete_plugin disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register WordPress MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More WordPress MCP Server tools

Destructive wordpress_bulk_delete_media wordpress_bulk_delete_media Destructive wordpress_bulk_delete_posts wordpress_bulk_delete_posts Destructive wordpress_clear_cache wordpress_clear_cache Destructive wordpress_delete_backup wordpress_delete_backup Destructive wordpress_delete_category wordpress_delete_category Destructive wordpress_delete_comment wordpress_delete_comment Destructive wordpress_delete_file wordpress_delete_file Destructive wordpress_delete_media wordpress_delete_media

All 190 WordPress MCP Server tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in WordPress MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the wordpress_delete_plugin tool do? +

wordpress_delete_plugin. It is categorised as a Destructive tool in the WordPress MCP Server 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 wordpress_delete_plugin? +

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

What risk level is wordpress_delete_plugin? +

wordpress_delete_plugin 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 wordpress_delete_plugin? +

Yes. Add a rate_limit block to the wordpress_delete_plugin 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 wordpress_delete_plugin completely? +

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

wordpress_delete_plugin is provided by the WordPress MCP Server MCP server (raheesahmed/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WordPress MCP Server tool call.

Deterministic rules across all 190 WordPress MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN WORDPRESS →

Free to start. No card required.

190 WordPress MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT WORDPRESS_DELETE_PLUGIN ON WORDPRESS MCP SERVER DOES

// THE RISK

// HOW TO CONTROL WORDPRESS_DELETE_PLUGIN

// EXPLORE