list_bridges
AI agents call list_bridges to retrieve information from Bridge Metrics MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or enumerate available bridges across blockchain networks based on its name and the read-only nature of sibling tools on this metrics-focused server. The empty description prevents higher confidence, but the naming pattern and server context strongly suggest this is a data retrieval operation with no side effects or state modification.
From the tool's definition Tool name 'list_bridges' with sibling tools 'get_day_stats', 'get_historical_volumes', 'get_transactions' indicates a query/retrieval function.
Attacks that exploit this kind of access
list_bridges. It is categorised as a Read tool in the Bridge Metrics MCP MCP Server, which means it retrieves data without modifying state.
Register the Bridge Metrics MCP server in PolicyLayer and add a rule for list_bridges: 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 Bridge Metrics MCP. Nothing to install.
list_bridges 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_bridges 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_bridges. 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_bridges is provided by the Bridge Metrics MCP server (kukapay/bridge-metrics-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 →