Get a single WordPress post by ID with full content.
AI agents call wordpress_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.
This tool retrieves post data by ID and returns content. It has no side effects, does not modify or delete data, and does not execute code or trigger external operations. It is a straightforward read operation that queries existing WordPress post data.
From the tool's definition Tool name 'wordpress_get_post' and description 'Get a single WordPress post by ID with full content' indicate retrieval of data without modification or deletion.
Attacks that exploit this kind of access
Get a single WordPress post by ID with full 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 wordpress_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.
wordpress_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 wordpress_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 wordpress_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.
wordpress_get_post is provided by the MCP Wordpress MCP server (crunchtools/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 →