List WordPress posts
AI agents call list_posts to retrieve information from WordPressMCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries WordPress posts without side effects. It does not create, modify, or delete data. It is a straightforward read operation that presents minimal security risk, only constrained by access controls on which posts are readable by the authenticated user.
From the tool's definition Tool name 'list_posts' and description 'List WordPress posts' indicate data retrieval with no modification. Sibling tools show destructive operations (delete_*) are separate, confirming this tool only queries existing posts.
Attacks that exploit this kind of access
List WordPress posts. It is categorised as a Read tool in the WordPressMCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPressMCP Server MCP server in PolicyLayer and add a rule for list_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 WordPressMCP Server. Nothing to install.
list_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 list_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 list_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.
list_posts is provided by the WordPressMCP Server MCP server (jahzlariosa/wordpress-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 →