Start a full batch export. Creates a job in SQLite, fetches all post IDs, and begins processing in batches. Returns after the first batch — use export_resume to continue.
AI agents use export_start to create or update resources in WP Astro MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WP Astro MCP environment.
This tool creates and modifies data (a job record in SQLite) and initiates a batch processing operation. While it doesn't delete data (ruling out Destructive) or execute arbitrary code (Execute would apply only if it runs user-supplied scripts), it does persistently write state to a database and trigger an automated workflow.
From the tool's definition export_start creates a job in SQLite, fetches all post IDs, and begins processing in batches, indicating persistent state creation and data mutation.
Documented attack patterns abuse exactly the kind of access export_start 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_start:
{
"version": "1",
"default": "deny",
"tools": {
"export_start": {
"limits": [
{
"counter": "export_start_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_start stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Start a full batch export. Creates a job in SQLite, fetches all post IDs, and begins processing in batches. Returns after the first batch — use export_resume to continue. It is categorised as a Write tool in the WP Astro MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WP Astro MCP server in PolicyLayer and add a rule for export_start: 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_start is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_start 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_start. 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_start 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.