List WordPress posts with optional filters. By default, this shows published posts; specify a status filter if you want to see drafts or other non-published posts.
AI agents call wp_list_posts to retrieve information from Claudaborative Editing without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval operation that queries existing WordPress posts. It allows filtering by status (published, drafts, etc.) but does not create, modify, delete, or execute any operations. The ability to see draft posts does not elevate the risk—it is still purely informational.
From the tool's definition Tool name 'wp_list_posts' and description stating 'List WordPress posts with optional filters' indicates retrieval and querying of data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access wp_list_posts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claudaborative Editing, and nothing reaches the server without passing your rules. This is the rule we recommend for wp_list_posts:
{
"version": "1",
"default": "deny",
"tools": {
"wp_list_posts": {}
}
} wp_list_posts 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.
List WordPress posts with optional filters. By default, this shows published posts; specify a status filter if you want to see drafts or other non-published posts. It is categorised as a Read tool in the Claudaborative Editing MCP Server, which means it retrieves data without modifying state.
Register the Claudaborative Editing MCP server in PolicyLayer and add a rule for wp_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 Claudaborative Editing. Nothing to install.
wp_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 wp_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 wp_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.
wp_list_posts is provided by the Claudaborative Editing MCP server (pento/claudaborative-editing). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claudaborative Editing, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 Claudaborative Editing tools catalogued and risk-classified — across an index of 43,000+ MCP servers.