List all Fabric Cloud Routers in your account
AI agents call list_fabric_routers to retrieve information from Equinix Fabric MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only operation to enumerate existing routers. It has no side effects, does not create, modify, or delete resources, and does not execute commands or trigger external operations. The blast radius of misuse is minimal—listing routers only exposes metadata about existing infrastructure without enabling unauthorized changes.
From the tool's definition Tool name is 'list_fabric_routers' and description states 'List all Fabric Cloud Routers in your account' — this is a query operation that retrieves information without modifying, deleting, or executing any infrastructure changes.
Attacks that exploit this kind of access
List all Fabric Cloud Routers in your account. It is categorised as a Read tool in the Equinix Fabric MCP MCP Server, which means it retrieves data without modifying state.
Register the Equinix Fabric MCP server in PolicyLayer and add a rule for list_fabric_routers: 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 Equinix Fabric MCP. Nothing to install.
list_fabric_routers 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_fabric_routers 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_fabric_routers. 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_fabric_routers is provided by the Equinix Fabric MCP server (sliuuu/equinix-fabric-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 →