get_bridge_routes

What get_bridge_routes does on Tenzro Ledger MCP

AI agents call get_bridge_routes to retrieve information from Tenzro Ledger MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_bridge_routes is rated Low

This tool retrieves and presents data about available bridge routes, fees, and timing between chains. It has no side effects—it does not execute transactions, move funds, modify data, or trigger external operations. It is a pure read operation analogous to a search or list function. While the Tenzro Ledger server handles sensitive operations like payments and staking, this specific tool is informational only.

From the tool's definition Tool name 'get_bridge_routes' and description 'Get available bridge routes between two chains with fees and timing' indicate a query/retrieval operation that returns informational data about bridge routes, fees, and timing without modifying state or executing…

The rule that runs get_bridge_routes safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_bridge_routes, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_bridge_routes": {}
  }
}

Questions about get_bridge_routes