AI agents invoke export_retry 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 re-triggers the execution of an export job for previously failed posts. It initiates an operational process (re-running export operations) rather than simply reading data or writing/deleting records. The blast radius is moderate — it could re-process many posts and potentially overwrite previously exported content, but is generally recoverable.
From the tool's definition Retry all failed posts in an export job
Documented attack patterns abuse exactly the kind of access export_retry 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_retry:
{
"version": "1",
"default": "deny",
"tools": {
"export_retry": {
"limits": [
{
"counter": "export_retry_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}export_retry 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.
Retry all failed posts in an export job. 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_retry: 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_retry 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_retry 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_retry. 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_retry 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.