Delete a bridge domain
AI agents call delete_bridge_domain to permanently remove resources in ACI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a bridge domain is an irreversible destructive action that removes a fundamental network construct in ACI, potentially causing network disruption and data loss. This falls squarely into the Destructive category (most severe applicable) as the operation cannot be undone and affects infrastructure configuration.
From the tool's definition Tool name 'delete_bridge_domain' and description 'Delete a bridge domain' indicate irreversible deletion of a network configuration object in Cisco ACI infrastructure.
Attacks that exploit this kind of access
Delete a bridge domain. It is categorised as a Destructive tool in the ACI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ACI MCP Server MCP server in PolicyLayer and add a rule for delete_bridge_domain: 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 ACI MCP Server. Nothing to install.
delete_bridge_domain 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_bridge_domain 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_bridge_domain. 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_bridge_domain is provided by the ACI MCP Server MCP server (jim-coyne/aci_mcp). 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 →