wpdev_site_delete

THE RISK

Critical Risk

This tool permanently deletes WordPress sites and optionally removes all associated files. Site deletion cannot be undone and destroys all data and configuration. While the confirm parameter adds a safeguard, an AI agent with confirmed deletion intent would irreversibly destroy a complete site.

From the tool's definition Tool description explicitly states 'Delete a Studio site' and uses the word 'Destructive'. The requirement for `confirm=true` indicates the system recognizes the irreversible nature of this operation.

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

HOW TO CONTROL WPDEV_SITE_DELETE

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

policy.json

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

wpdev_site_delete 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 Developer 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 Developer MCP Server tools

Destructive wpdev_auth_logout Log out and clear WordPress.com authentication for Studio. Destructive wpdev_fs_delete Delete a file or folder inside a Studio site directory. Safe: only allows paths within the Destructive wpdev_preview_delete Delete a Studio preview site by its hostname (e.g. Execute wpdev_site_start Start a Studio site. Returns site URL and admin username. Execute wpdev_site_stop Stop a Studio site or all sites. Execute wpdev_wp Run WP-CLI commands on a Studio site. Use deliberately because WP-CLI can be slower than f Execute wpdev_site_inspect Inspect a local WordPress site route with a real browser. Use this after creating or chang Execute wpdev_update_mcp Update the WordPress Developer MCP Server to the latest version.

All 25 WordPress Developer 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 Developer 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 wpdev_site_delete tool do? +

Delete a Studio site. Destructive: requires confirm=true. Optionally move site files to trash. It is categorised as a Destructive tool in the WordPress Developer 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 wpdev_site_delete? +

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

What risk level is wpdev_site_delete? +

wpdev_site_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 wpdev_site_delete? +

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

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

wpdev_site_delete is provided by the WordPress Developer MCP Server MCP server (nightnei/wordpress-developer-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 Developer MCP Server tool call.

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

GOVERN WORDPRESS DEVELOPER →

Free to start. No card required.

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

// WHAT WPDEV_SITE_DELETE ON WORDPRESS DEVELOPER MCP SERVER DOES

// THE RISK

// HOW TO CONTROL WPDEV_SITE_DELETE

// EXPLORE