Release dedicated BGP peer
AI agents call release_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.
Releasing a BGP peer removes the dedicated network peering relationship from the infrastructure. In networking contexts, 'release' of a dedicated resource means deallocating it, which can disrupt routing, connectivity, and network services. This is not easily reversible and has significant blast radius as BGP peers are critical networking components that affect routing for potentially many VMs and workloads.
From the tool's definition "Release dedicated BGP peer" - releasing a dedicated resource typically removes/deallocates it irreversibly
Attacks that exploit this kind of access
Release dedicated BGP peer. 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 release_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.
release_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 release_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 release_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.
release_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →