site_remove

THE RISK

Critical Risk

Why site_remove needs a policy

This tool performs a site-level deactivation action that, while technically reversible, constitutes an irreversible operational change from the user's perspective without requiring explicit reactivation. The term 'Deactivate' combined with 'remove' indicates the tool is designed to take a site offline. Although 'soft delete' suggests recoverability, the primary action is destructive to site availability.

From the tool's definition Tool name 'site_remove' combined with description 'Deactivate a site (soft delete, can be reactivated)' indicates removal of a site from the system.

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

POLICY

How to control site_remove

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

policy.json

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

site_remove 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 sync_delete Remove local Markdown files for posts that have been deleted or trashed in WordPress. Also Destructive sync_full Complete content sync: check for changes → pull new/updated posts → delete removed posts → 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 site_remove

What does the site_remove tool do? +

Deactivate a site (soft delete, can be reactivated). 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 site_remove? +

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

site_remove 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 site_remove? +

Yes. Add a rate_limit block to the site_remove 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 site_remove completely? +

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

site_remove 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 →