Critical Risk →

wpdev_fs_delete

Delete a file or folder inside a Studio site directory. Safe: only allows paths within the given sitePath.

How to control wpdev_fs_delete ↓

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

Critical Risk

This tool irreversibly deletes files or folders, which is the defining characteristic of the Destructive category. While the tool includes a safety restriction (only paths within sitePath), the core functionality remains data destruction. The high severity reflects that an AI agent could accidentally delete critical WordPress configuration files, themes, plugins, or content.

From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a file or folder'. The operation is irreversible and removes data permanently.

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

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_fs_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "wpdev_fs_delete"
  ]
}

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

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

Free to start. No card required.

Go deeper

What does the wpdev_fs_delete tool do? +

Delete a file or folder inside a Studio site directory. Safe: only allows paths within the given sitePath. 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_fs_delete? +

Register the WordPress Developer MCP Server MCP server in PolicyLayer and add a rule for wpdev_fs_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_fs_delete? +

wpdev_fs_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_fs_delete? +

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

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

wpdev_fs_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.

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.