Fetches the list of bridges supported by LiFi for cross-chain bridging
AI agents call getSupportedBridges to retrieve information from Bridge Rates without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to retrieve metadata about supported bridges. It has no capacity to modify, delete, or execute external operations, making it a straightforward Read classification with low severity.
From the tool's definition Tool name is 'getSupportedBridges' and description states 'Fetches the list of bridges' — a query operation that retrieves data with no side effects.
Attacks that exploit this kind of access
Fetches the list of bridges supported by LiFi for cross-chain bridging. It is categorised as a Read tool in the Bridge Rates MCP Server, which means it retrieves data without modifying state.
Register the Bridge Rates MCP server in PolicyLayer and add a rule for getSupportedBridges: 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 Rates. Nothing to install.
getSupportedBridges 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 getSupportedBridges 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 getSupportedBridges. 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.
getSupportedBridges is provided by the Bridge Rates MCP server (kukapay/bridge-rates-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 →