wordpress_search_replace
Perform WordPress search and replace operation
This record as markdown: /tools/cbrown35-20i-mcp/wordpress-search-replace.md
What wordpress_search_replace does on 20i MCP Server
AI agents invoke wordpress_search_replace to trigger actions in 20i MCP Server. 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 wordpress_search_replace is rated High
A search-and-replace operation in WordPress typically runs against the database, modifying multiple records across posts, options, metadata, and serialized data. It is not a simple write to a known field — it executes a bulk transformation that can irreversibly alter site content, URLs, or configuration at scale.
From the tool's definition 'Perform WordPress search and replace operation' — this executes a database-level find-and-replace across WordPress content
Attacks that exploit this kind of access
The rule that runs wordpress_search_replace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wordpress_search_replace, this is the rule to start with:
wordpress_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.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every wordpress_search_replace call is checked against it from then on.
Questions about wordpress_search_replace
Perform WordPress search and replace operation. It is categorised as a Execute tool in the 20i MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for wordpress_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 20i MCP Server. Nothing to install.
wordpress_search_replace is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wordpress_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.
Set action: deny in the PolicyLayer policy for wordpress_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.
wordpress_search_replace is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
Across the catalogue