Get details of a specific bridge domain
AI agents call get_bridge_domain to retrieve information from ACI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and returns information about a bridge domain in Cisco ACI. It has no side effects, does not execute commands, create/modify/delete resources, or affect infrastructure. The blast radius of misuse is minimal—an agent could only over-query or cause denial of service through excessive requests, not compromise infrastructure.
From the tool's definition Tool name 'get_bridge_domain' and description 'Get details of a specific bridge domain' indicate retrieval of existing configuration data with no modification or deletion.
Attacks that exploit this kind of access
Get details of a specific bridge domain. It is categorised as a Read tool in the ACI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ACI MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_bridge_domain is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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 →