Retrieve a paginated list of posts from WordPress.
AI agents call get_wordpress_posts to retrieve information from WordPress AI Content System without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing WordPress posts in a paginated format. It has no side effects—it performs a query-only operation that reads data without creating, modifying, deleting, or executing actions. The blast radius of misuse is minimal; an attacker could enumerate posts but cannot alter content or trigger external operations.
From the tool's definition Tool name 'get_wordpress_posts' and description 'Retrieve a paginated list of posts from WordPress' explicitly indicate a data retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Retrieve a paginated list of posts from WordPress. It is categorised as a Read tool in the WordPress AI Content System MCP Server, which means it retrieves data without modifying state.
Register the WordPress AI Content System MCP server in PolicyLayer and add a rule for get_wordpress_posts: 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 WordPress AI Content System. Nothing to install.
get_wordpress_posts 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_wordpress_posts 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_wordpress_posts. 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_wordpress_posts is provided by the WordPress AI Content System MCP server (ssolis-ti/wordpress_content_ai_mcp). 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 →