wpdev_site_stop

THE RISK

High Risk

Stopping a running site halts its operations and availability—a significant side effect, but reversible (sites can be restarted). This is Execute rather than Destructive because stopping is not irreversible data loss. It is Execute rather than Write because it does not create or modify data; it changes operational state.

From the tool's definition Tool name 'wpdev_site_stop' and description 'Stop a Studio site or all sites' indicate the tool triggers external operations (stopping running WordPress services/processes) whose effects depend on which site(s) are targeted.

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

HOW TO CONTROL WPDEV_SITE_STOP

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wpdev_site_stop": {
      "limits": [
        {
          "counter": "wpdev_site_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

wpdev_site_stop stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

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.

RATE-LIMIT 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. Destructive wpdev_site_delete Delete a Studio site. Destructive: requires confirm=true. Optionally move site files to tr Execute wpdev_site_start Start a Studio site. Returns site URL and admin username. 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 →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in WordPress Developer MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-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_stop tool do? +

Stop a Studio site or all sites. It is categorised as a Execute tool in the WordPress Developer MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wpdev_site_stop? +

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

wpdev_site_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wpdev_site_stop? +

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

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

wpdev_site_stop 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_STOP ON WORDPRESS DEVELOPER MCP SERVER DOES

// THE RISK

// HOW TO CONTROL WPDEV_SITE_STOP

// EXPLORE