Resume an in-progress export. Processes the next batch of pending posts. Call repeatedly until complete.
AI agents invoke export_resume to trigger actions in WP Astro MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an ongoing export operation, processing batches of posts through an external pipeline. It executes a multi-step process that extracts and transforms data, constituting an Execute action rather than a simple Read or Write. Misuse could cause repeated or uncontrolled processing of content batches, though it is not inherently destructive or financial.
From the tool's definition Resume an in-progress export. Processes the next batch of pending posts. Call repeatedly until complete.
Documented attack patterns abuse exactly the kind of access export_resume 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 export_resume:
{
"version": "1",
"default": "deny",
"tools": {
"export_resume": {
"limits": [
{
"counter": "export_resume_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}export_resume stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Resume an in-progress export. Processes the next batch of pending posts. Call repeatedly until complete. It is categorised as a Execute tool in the WP Astro MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WP Astro MCP server in PolicyLayer and add a rule for export_resume: 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.
export_resume is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the export_resume 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 export_resume. 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.
export_resume 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.