wordpress_search_replace

Perform WordPress search and replace operation

SERVER20i MCP Server SOURCEcbrown35/20i-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about wordpress_search_replace

What does the wordpress_search_replace tool do? +

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.

How do I enforce a policy on wordpress_search_replace? +

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.

What risk level is wordpress_search_replace? +

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

Can I rate-limit wordpress_search_replace? +

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.

How do I block wordpress_search_replace completely? +

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.

What MCP server provides wordpress_search_replace? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 20i MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.