release_bgp_peer

Release dedicated BGP peer

SERVERCloudStack MCP Server SOURCEmozg31337/cloudstack-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mozg31337-cloudstack-mcp-server/release-bgp-peer.md

WHAT IT DOES

What release_bgp_peer does on CloudStack MCP Server

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.

RISK

Why release_bgp_peer is rated Critical

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

RECOMMENDED RULE

The rule that runs release_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 release_bgp_peer, this is the rule to start with:

release_bgp_peer Hidden

release_bgp_peer is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CloudStack MCP Server, apply this rule, and every release_bgp_peer call is checked against it from then on.

FAQ

Questions about release_bgp_peer

What does the release_bgp_peer tool do? +

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.

How do I enforce a policy on release_bgp_peer? +

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.

What risk level is release_bgp_peer? +

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.

Can I rate-limit release_bgp_peer? +

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.

How do I block release_bgp_peer completely? +

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.

What MCP server provides release_bgp_peer? +

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.

KEEP EXPLORING

More on CloudStack MCP Server, and thousands of servers like it.

This server

All 442 CloudStack MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →