delete_site_collections_bulk
A destructive tool on the API-Central MCP server.
This record as markdown: /tools/secure-ssid-centralmcp/delete-site-collections-bulk.md
What delete_site_collections_bulk does on API-Central
AI agents call delete_site_collections_bulk to permanently remove resources in API-Central, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_site_collections_bulk is rated Critical
The tool performs bulk deletion of site collections, which is irreversible and affects network infrastructure at scale. In an HPE Aruba Central network operations context, site collections represent significant organizational units. Bulk deletion without reversibility qualifies as Destructive with critical severity due to the broad blast radius and inability to undo the operation.
From the tool's definition Tool name 'delete_site_collections_bulk' contains 'delete' and 'bulk', indicating irreversible deletion of multiple site collections. Description is empty, but the name unambiguously implies destructive action.
Attacks that exploit this kind of access
The rule that runs delete_site_collections_bulk safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_site_collections_bulk, this is the rule to start with:
delete_site_collections_bulk 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 API-Central, apply this rule, and every delete_site_collections_bulk call is checked against it from then on.
Questions about delete_site_collections_bulk
delete_site_collections_bulk is a destructive tool on the API-Central MCP server. It is categorised as a Destructive tool in the API-Central MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the API-Central MCP server in PolicyLayer and add a rule for delete_site_collections_bulk: 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 API-Central. Nothing to install.
delete_site_collections_bulk 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_site_collections_bulk 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_site_collections_bulk. 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_site_collections_bulk is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API-Central, and thousands of servers like it.
Across the catalogue