Fetch and write only changed content from WordPress. Creates new files for new posts, overwrites files for updated posts. Handles slug changes (deletes old file, writes new one). Updates URL map and content hashes.
AI agents use sync_pull 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 modifies the target Astro project by creating and overwriting files, which is reversible (developers can restore from version control or re-run migrations). The file deletion for slug changes is incidental to the write operation, not a primary destructive action against unrecoverable data.
From the tool's definition "Creates new files for new posts, overwrites files for updated posts" and "deletes old file, writes new one" indicate file creation and modification operations.
Documented attack patterns abuse exactly the kind of access sync_pull 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 sync_pull:
{
"version": "1",
"default": "deny",
"tools": {
"sync_pull": {
"limits": [
{
"counter": "sync_pull_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sync_pull 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.
Fetch and write only changed content from WordPress. Creates new files for new posts, overwrites files for updated posts. Handles slug changes (deletes old file, writes new one). Updates URL map and content hashes. 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 sync_pull: 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.
sync_pull 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 sync_pull 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 sync_pull. 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.
sync_pull 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.