List all available Equinix Fabric metro locations
AI agents call list_metros 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.
This tool retrieves reference data about metro locations without modifying, creating, deleting, or executing any operations. It is a straightforward informational query with no capability to alter infrastructure or cause unintended effects. Severity is low as the blast radius is limited to information disclosure of public infrastructure metadata.
From the tool's definition Tool name 'list_metros' and description 'List all available Equinix Fabric metro locations' indicates a read-only query operation that retrieves reference data about metro locations with no side effects.
Attacks that exploit this kind of access
List all available Equinix Fabric metro locations. 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_metros: 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_metros 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_metros 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_metros. 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_metros 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 →