Fetch authors/users from the site. Returns a bounded page (default 1000, max 10000) plus total/has_more/next_offset metadata — use offset to page through all authors.
AI agents call extract_authors 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 user/author data from a WordPress site via REST API without creating, modifying, deleting, or executing any operations. It is purely a read operation that enables pagination through existing data. The bounded page size and pagination metadata indicate a safe query interface.
From the tool's definition Tool description states it "Fetch[es] authors/users from the site" and "Returns a bounded page...plus total/has_more/next_offset metadata". No modification, deletion, or execution of operations occurs.
Documented attack patterns abuse exactly the kind of access extract_authors 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_authors:
{
"version": "1",
"default": "deny",
"tools": {
"extract_authors": {}
}
}extract_authors 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 authors/users from the site. Returns a bounded page (default 1000, max 10000) plus total/has_more/next_offset metadata — use offset to page through all authors. 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_authors: 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_authors 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_authors 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_authors. 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_authors 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.