List available WordPress documentation pages, optionally filtered by type, category, or source. Returns titles and slugs grouped by category. Use search_docs for full-text search or get_doc to read a specific page. Tip: filter by category for complete listings — unfiltered results may be truncated.
AI agents call list_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 retrieves and queries documentation metadata with no side effects. It performs a listing operation that returns informational content (titles and slugs) grouped by category, which is a Read operation. There is no capability to create, modify, delete, execute code, or affect financial systems.
From the tool's definition Tool name is 'list_docs' and description states it 'List available WordPress documentation pages' and 'Returns titles and slugs grouped by category.' The description explicitly suggests using 'search_docs for full-text search or get_doc to read a specific…
Documented attack patterns abuse exactly the kind of access list_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 list_docs:
{
"version": "1",
"default": "deny",
"tools": {
"list_docs": {}
}
}list_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.
List available WordPress documentation pages, optionally filtered by type, category, or source. Returns titles and slugs grouped by category. Use search_docs for full-text search or get_doc to read a specific page. Tip: filter by category for complete listings — unfiltered results may be truncated. 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 list_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.
list_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 list_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 list_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.
list_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.