Search WordPress hooks (actions/filters) across all indexed sources using full-text search. Returns BM25-ranked results with file locations, parameters, and descriptions.
AI agents call search_hooks 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.
search_hooks retrieves and queries indexed WordPress hook data, returning ranked search results with metadata (file locations, parameters, descriptions). This is a pure read operation with no side effects, data modification, or code execution capabilities.
From the tool's definition Tool performs 'full-text search' and 'returns' results with no modification capability; the description explicitly states it 'search[es]' without create/update/delete/execute operations.
Documented attack patterns abuse exactly the kind of access search_hooks 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_hooks:
{
"version": "1",
"default": "deny",
"tools": {
"search_hooks": {}
}
}search_hooks 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 hooks (actions/filters) across all indexed sources using full-text search. Returns BM25-ranked results with file locations, parameters, and descriptions. 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_hooks: 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_hooks 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_hooks 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_hooks. 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_hooks 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.