Get the full content of a WordPress documentation page by its ID (numeric) or slug. Returns the complete markdown content along with metadata.
AI agents call get_doc 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 performs a read-only retrieval operation on static WordPress documentation pages. It has no side effects, cannot modify data, execute code, or cause irreversible changes. The query operation is purely informational, making it a standard Read operation with low severity even if misused by an AI agent.
From the tool's definition Tool retrieves documentation content by ID or slug and returns markdown content with metadata. The description explicitly states it 'Get[s] the full content' with no mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_doc 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 get_doc:
{
"version": "1",
"default": "deny",
"tools": {
"get_doc": {}
}
}get_doc 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.
Get the full content of a WordPress documentation page by its ID (numeric) or slug. Returns the complete markdown content along with metadata. 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 get_doc: 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.
get_doc 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 get_doc 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 get_doc. 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.
get_doc 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.