Search WordPress official documentation (handbooks, REST API docs, WP-CLI reference, block editor guides, etc.) using full-text search. Returns BM25-ranked results. Use get_doc to retrieve full content for a specific result.
AI agents call search_docs to retrieve information from Wp Devdocs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a documentation database and returns search results without modifying, executing, or deleting any data. It is a retrieval operation with no capability to alter state or trigger external actions. The low severity reflects that misuse would only expose publicly available WordPress documentation.
From the tool's definition Tool performs 'full-text search' and 'returns BM25-ranked results' on WordPress documentation. The description explicitly states to 'Use get_doc to retrieve full content', indicating this tool only retrieves and queries existing documentation with no side…
Documented attack patterns abuse exactly the kind of access search_docs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wp Devdocs, and nothing reaches the server without passing your rules. This is the rule we recommend for search_docs:
{
"version": "1",
"default": "deny",
"tools": {
"search_docs": {}
}
}search_docs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search WordPress official documentation (handbooks, REST API docs, WP-CLI reference, block editor guides, etc.) using full-text search. Returns BM25-ranked results. Use get_doc to retrieve full content for a specific result. It is categorised as a Read tool in the Wp Devdocs MCP Server, which means it retrieves data without modifying state.
Register the Wp Devdocs MCP server in PolicyLayer and add a rule for search_docs: 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 Devdocs. Nothing to install.
search_docs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_docs 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 search_docs. 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.
search_docs is provided by the Wp Devdocs MCP server (pluginslab/wp-devdocs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Wp Devdocs tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 Wp Devdocs tools catalogued and risk-classified — across an index of 42,500+ MCP servers.