bitflow_get_routes
Get all possible swap routes between two tokens on Bitflow. Returns all available routes for swapping from tokenX to tokenY, including multi-hop routes through intermediate tokens. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/bitflow-get-routes.md
What bitflow_get_routes does on Aibtc
AI agents call bitflow_get_routes to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why bitflow_get_routes is rated Low
This tool retrieves and queries information about available swap routes on Bitflow. It has no side effects, does not modify any state, and does not execute transactions. It is a straightforward data retrieval operation similar to search or fetch operations. The public endpoint availability and rate limit (500 req/min) further confirm it is a read-only query interface.
From the tool's definition Tool description explicitly states 'Get all possible swap routes' and 'Returns all available routes'. Uses 'public endpoints' with no side effects. No creation, modification, deletion, code execution, or financial transactions occur.
Attacks that exploit this kind of access
The rule that runs bitflow_get_routes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bitflow_get_routes, this is the rule to start with:
bitflow_get_routes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every bitflow_get_routes call is checked against it from then on.
Questions about bitflow_get_routes
Get all possible swap routes between two tokens on Bitflow. Returns all available routes for swapping from tokenX to tokenY, including multi-hop routes through intermediate tokens. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for bitflow_get_routes: 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 Aibtc. Nothing to install.
bitflow_get_routes 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 bitflow_get_routes 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 bitflow_get_routes. 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.
bitflow_get_routes is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue