delete_bgp_peer
A destructive tool on the CloudStack MCP server.
This record as markdown: /tools/mozg31337-cloudstack-mcp-server/delete-bgp-peer.md
What delete_bgp_peer does on CloudStack MCP Server
AI agents call delete_bgp_peer to permanently remove resources in CloudStack MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_bgp_peer is rated Critical
Deleting a BGP peer is a destructive operation that irreversibly removes network routing relationships and configuration. This falls under the Destructive category as it cannot be reversed without manual intervention and reconfiguration.
From the tool's definition Tool name explicitly uses 'delete' combined with 'BGP peer', indicating irreversible removal of network routing configuration. BGP (Border Gateway Protocol) peers are critical network infrastructure components whose deletion cannot be automatically undone.
Attacks that exploit this kind of access
The rule that runs delete_bgp_peer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_bgp_peer, this is the rule to start with:
delete_bgp_peer 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 CloudStack MCP Server, apply this rule, and every delete_bgp_peer call is checked against it from then on.
Questions about delete_bgp_peer
delete_bgp_peer is a destructive tool on the CloudStack MCP Server MCP server. It is categorised as a Destructive tool in the CloudStack MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for delete_bgp_peer: 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 CloudStack MCP Server. Nothing to install.
delete_bgp_peer 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_bgp_peer 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_bgp_peer. 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_bgp_peer is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CloudStack MCP Server, and thousands of servers like it.
Across the catalogue