Check if a WordPress hook name is valid (exists in indexed sources). Returns VALID, NOT_FOUND, or REMOVED status with similar suggestions when not found. Use this to prevent hook name hallucination.
AI agents call validate_hook 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.
validate_hook is a query/lookup tool that retrieves information about WordPress hook validity from a source-code index. It has no side effects, does not execute code, does not modify data, and does not trigger external operations. It serves an informational purpose to prevent hallucination by verifying hook names against known indexed sources. This is characteristic of Read category tools.
From the tool's definition Tool performs validation and lookup operations ('Check if a WordPress hook name is valid', 'Returns VALID, NOT_FOUND, or REMOVED status') against an indexed database without modifying, creating, deleting, or executing any code or operations.
Documented attack patterns abuse exactly the kind of access validate_hook 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 validate_hook:
{
"version": "1",
"default": "deny",
"tools": {
"validate_hook": {}
}
}validate_hook 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.
Check if a WordPress hook name is valid (exists in indexed sources). Returns VALID, NOT_FOUND, or REMOVED status with similar suggestions when not found. Use this to prevent hook name hallucination. 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 validate_hook: 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.
validate_hook 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 validate_hook 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 validate_hook. 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.
validate_hook 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.