delete_sites
Permanently delete sites by ID (e.g. clean up failed test sites) — the MCP equivalent of the dashboard trash button. Explicit siteIds only; every id must belong to the given project. This cannot be undone. Use list_sites to find the IDs.
This record as markdown: /tools/a3plus-mcp/delete-sites.md
What delete_sites does on A3plus
AI agents call delete_sites to permanently remove resources in A3plus, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
siteIds | array | Yes | Site IDs to delete (required, non-empty). |
projectId | string | Yes | The A3Plus project ID the sites belong to. |
Parameters from the server's own tool schema.
Why delete_sites is rated Critical
An AI agent that decides to call delete_sites doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from A3plus is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_sites safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A3plus, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_sites, this is the rule to start with:
delete_sites is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect A3plus, apply this rule, and every delete_sites call is checked against it from then on.
Questions about delete_sites
Permanently delete sites by ID (e.g. clean up failed test sites) — the MCP equivalent of the dashboard trash button. Explicit siteIds only; every id must belong to the given project. This cannot be undone. Use list_sites to find the IDs. It is categorised as a Destructive tool in the A3plus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_sites accepts 2 parameters: siteIds, projectId. Required: siteIds, projectId. The full parameter table on this page comes from the server's own tool schema.
Register the A3plus MCP server in PolicyLayer and add a rule for delete_sites: 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 A3plus. Nothing to install.
delete_sites is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_sites 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 delete_sites. 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.
delete_sites is provided by the A3plus MCP server (a3plus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A3plus, and thousands of servers like it.
Across the catalogue