List bridge domains in a tenant
AI agents call list_bridge_domains 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 tool retrieves and enumerates bridge domains within a specified tenant. It performs a read-only query operation against the APIC REST API with no side effects. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could enumerate network infrastructure but cannot alter configurations or trigger actions.
From the tool's definition Tool name includes 'list' and description states 'List bridge domains in a tenant' - indicating a retrieval operation that queries existing data without modification.
Attacks that exploit this kind of access
List bridge domains in a tenant. 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 list_bridge_domains: 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.
list_bridge_domains 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 list_bridge_domains 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 list_bridge_domains. 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.
list_bridge_domains 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 →