Fetch ALL authors and cache them in SQLite. Should be run before a full export for fast author lookups. Caches every author but returns only a count plus a small sample (first 20).
AI agents call cache_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 fetches author data from WordPress via REST API and stores it locally in a SQLite cache for performance purposes. It reads remote data and writes to a local cache file, but has no side effects on the source system. The most significant action is the local cache write, which is reversible and low risk. Severity is low as misuse would at worst cause unnecessary network requests or local storage use.
From the tool's definition Fetch ALL authors and cache them in SQLite... returns only a count plus a small sample (first 20)
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access cache_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 cache_authors:
{
"version": "1",
"default": "deny",
"tools": {
"cache_authors": {}
}
}cache_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 ALL authors and cache them in SQLite. Should be run before a full export for fast author lookups. Caches every author but returns only a count plus a small sample (first 20). 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 cache_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.
cache_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 cache_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 cache_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.
cache_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.