// MCP TOOL REFERENCE

sync_full

Complete content sync: check for changes → pull new/updated posts → delete removed posts → update caches → optionally commit to git. One command to keep the Astro site current with WordPress.

ServerWP Astro MCP
CategoryDestructive

How to control sync_full ↓

WHAT IT DOES

What sync_full does on WP Astro MCP

AI agents call sync_full to permanently remove resources in WP Astro MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

Why sync_full needs a policy

While this tool has Read (check for changes, pull posts) and Write (update caches) components, the explicit capability to 'delete removed posts' places it in the Destructive category. Deleting content is irreversible and represents the most severe potential harm. The git commit adds another dimension of permanence.

From the tool's definition Tool performs 'delete removed posts' and 'optionally commit to git'. The deletion of posts is irreversible content removal.

Documented attack patterns abuse exactly the kind of access sync_full gives an agent:

POLICY

How to control sync_full

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_full:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "sync_full"
  ]
}

sync_full disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register WP Astro MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More WP Astro MCP tools

Destructive site_remove Deactivate a site (soft delete, can be reactivated). Destructive sync_delete Remove local Markdown files for posts that have been deleted or trashed in WordPress. Also Destructive sync_reset Clear sync tracking data to force a full re-sync on next sync_pull. Does not delete conten Destructive export_cleanup Delete export job data from database (does not delete files). Requires confirm=true. Execute wp_astro_run Execute a WordPress-to-Astro frontend action. Use wp_astro_help to list available actions. Execute export_resume Resume an in-progress export. Processes the next batch of pending posts. Call repeatedly u Execute export_retry Retry all failed posts in an export job. Execute github_push Push commits to the remote repository.

All 60 WP Astro MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in WP Astro MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sync_full

What does the sync_full tool do? +

Complete content sync: check for changes → pull new/updated posts → delete removed posts → update caches → optionally commit to git. One command to keep the Astro site current with WordPress. It is categorised as a Destructive tool in the WP Astro MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on sync_full? +

Register the WP Astro MCP server in PolicyLayer and add a rule for sync_full: 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.

What risk level is sync_full? +

sync_full is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit sync_full? +

Yes. Add a rate_limit block to the sync_full 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.

How do I block sync_full completely? +

Set action: deny in the PolicyLayer policy for sync_full. 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.

What MCP server provides sync_full? +

sync_full 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.

Enforce policy on every WP Astro MCP tool call.

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.

CHECK YOUR STACK →

Free to start. No card required.

60 WP Astro MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.