Get full content of a WordPress post by ID. Returns raw content.
AI agents call wp_get_post to retrieve information from Mcp Wordpress without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
wp_get_post retrieves post data without side effects. It does not create, modify, delete, or execute operations. The read-only nature and limited blast radius (information disclosure only) from a legitimate WordPress post justifies low severity.
From the tool's definition Tool description states 'Get full content of a WordPress post by ID. Returns raw content.' This is a retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get full content of a WordPress post by ID. Returns raw content. It is categorised as a Read tool in the Mcp Wordpress MCP Server, which means it retrieves data without modifying state.
Register the Mcp Wordpress MCP server in PolicyLayer and add a rule for wp_get_post: 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 Mcp Wordpress. Nothing to install.
wp_get_post 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 wp_get_post 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 wp_get_post. 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.
wp_get_post is provided by the Mcp Wordpress MCP server (leonardobora/mcp-wordpress). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →