Fetch posts from WordPress with pagination. Supports any post type, status filters, date filters. Returns posts with embedded author, featured image, and terms.
AI agents call extract_posts to retrieve information from WP Astro MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves WordPress post data via REST API without creating, modifying, or destroying any content. Pagination and filtering are read-only query parameters. The blast radius of misuse is minimal — an agent could retrieve unwanted data but cannot alter WordPress state or trigger external operations. This is a straightforward Read operation.
From the tool's definition Tool description states 'Fetch posts from WordPress' and 'Returns posts with embedded author, featured image, and terms' — these are retrieval operations.
Documented attack patterns abuse exactly the kind of access extract_posts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WP Astro MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for extract_posts:
{
"version": "1",
"default": "deny",
"tools": {
"extract_posts": {}
}
}extract_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.
Fetch posts from WordPress with pagination. Supports any post type, status filters, date filters. Returns posts with embedded author, featured image, and terms. It is categorised as a Read tool in the WP Astro MCP MCP Server, which means it retrieves data without modifying state.
Register the WP Astro MCP server in PolicyLayer and add a rule for extract_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 WP Astro MCP. Nothing to install.
extract_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 extract_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 extract_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.
extract_posts is provided by the WP Astro MCP server (vapvarun/wp-astro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WP Astro MCP, 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.
60 WP Astro MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.