wp_search_replace · Wp Cli MCP: Risk & Policy

WHAT IT DOES

What wp_search_replace does on Wp Cli

AI agents invoke wp_search_replace to trigger actions in Wp Cli. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why wp_search_replace needs a policy

This tool executes a bulk find-and-replace operation across all database tables. While it modifies data (Write), the operation is a mass, potentially irreversible database mutation affecting the entire WordPress database. It can corrupt or transform content site-wide, and without an explicit undo mechanism described, it sits at the boundary of Execute/Destructive.

From the tool's definition Search and replace strings across all WordPress database tables. Essential for domain migrations (e.g. staging to production). Handles serialized data correctly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wp_search_replace Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Wp Cli, so you can run agents against it safely.

FAQ

Questions about wp_search_replace

What does the wp_search_replace tool do? +

Search and replace strings across all WordPress database tables. Essential for domain migrations (e.g. staging to production). Handles serialized data correctly. It is categorised as a Execute tool in the Wp Cli MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wp_search_replace? +

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

What risk level is wp_search_replace? +

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

Can I rate-limit wp_search_replace? +

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

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

wp_search_replace is provided by the Wp Cli MCP server (mvtandas/wp-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.