wp_list_posts
Holt eine Liste aller WordPress-Beiträge mit optionalen Filtern
This record as markdown: /tools/c-sakel-wp-mcp-server/wp-list-posts.md
What wp_list_posts does on WordPress MCP Server
AI agents call wp_list_posts to retrieve information from WordPress MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wp_list_posts is rated Low
This tool retrieves or queries post data from WordPress with no side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The use of 'list' and optional filters confirms it is a retrieval operation. There is no indication the tool creates, modifies, deletes, executes commands, or moves money.
From the tool's definition Tool name 'wp_list_posts' and description 'retrieves a list of all WordPress posts with optional filters' indicate a read-only query operation that returns existing data without modification.
Attacks that exploit this kind of access
The rule that runs wp_list_posts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wp_list_posts, this is the rule to start with:
wp_list_posts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every wp_list_posts call is checked against it from then on.
Questions about wp_list_posts
Holt eine Liste aller WordPress-Beiträge mit optionalen Filtern. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server 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 WordPress MCP Server. 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 WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WordPress MCP Server, and thousands of servers like it.
This server
Across the catalogue