Execute a WordPress-to-Astro frontend action. Use wp_astro_help to list available actions. Common workflows: 1. Add site: site_add → site_analyze → site_export_config 2. Preview: convert_preview (see sample converted posts) 3. Export: export_plan → export_start → export_resume → export_validate 4...
AI agents invoke wp_astro_run 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 is an Execute tool because it triggers complex multi-step operations with external side effects: it can initialize GitHub repos, push code, delete files (via sync_full), and commit changes. While some sub-actions like 'site_list' and 'sync_check' are Read operations, the tool itself is a dispatcher for Execute-class operations.
From the tool's definition Tool name 'wp_astro_run' combined with description 'Execute a WordPress-to-Astro frontend action' and workflows showing commands like 'github_init', 'github_create_repo', 'github_push', 'sync_full' (which performs 'check + pull + delete + commit in one step')…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access wp_astro_run 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 wp_astro_run:
{
"version": "1",
"default": "deny",
"tools": {
"wp_astro_run": {
"limits": [
{
"counter": "wp_astro_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}wp_astro_run 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.
Execute a WordPress-to-Astro frontend action. Use wp_astro_help to list available actions. Common workflows: 1. Add site: site_add → site_analyze → site_export_config 2. Preview: convert_preview (see sample converted posts) 3. Export: export_plan → export_start → export_resume → export_validate 4. Publish: github_init → github_create_repo → github_push 5. Ongoing sync: sync_check → sync_pull → github_push 6. Auto sync: sync_full (check + pull + delete + commit in one step) Quick actions: - site_list — see all registered sites - sync_check — see what changed in WordPress since last sync - sync_full — sync everything and optionally auto-commit Note: common actions (site_add, site_list, site_analyze, content_audit, export_plan/start/resume/progress, sync_check, sync_full, github_push) are also exposed as standalone tools with full schemas — prefer those when available. Use wp_astro_help for the full action list and wp_astro_describe({ action }) for any action. 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 wp_astro_run: 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.
wp_astro_run 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 wp_astro_run 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 wp_astro_run. 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.
wp_astro_run 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.