Fetches the cross-chain bridge rate for a token pair between two chains
AI agents call getBridgeRates 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 queries and returns bridge rate information. The verb 'fetches' and the absence of any language suggesting modification, deletion, or execution of code/transactions indicates a read-only operation. No financial transactions occur; it only retrieves rates for informational purposes. The low severity reflects that misuse would only expose rate data without enabling unauthorized actions.
From the tool's definition Tool name 'getBridgeRates' and description 'Fetches the cross-chain bridge rate for a token pair between two chains' indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetches the cross-chain bridge rate for a token pair between two chains. 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 getBridgeRates: 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.
getBridgeRates 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 getBridgeRates 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 getBridgeRates. 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.
getBridgeRates 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 →