bitflow_get_swap_targets
Get possible swap target tokens for a given input token on Bitflow. Returns all tokens that can be received when swapping from the specified token. 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-swap-targets.md
What bitflow_get_swap_targets does on Aibtc
AI agents call bitflow_get_swap_targets 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_swap_targets is rated Low
This tool retrieves data about possible swap targets without modifying state, executing code, or creating financial obligations. It is a read-only query of publicly available information on the Bitflow protocol. The blast radius of misuse is minimal since the agent can only retrieve information, not execute swaps or alter blockchain state.
From the tool's definition Tool name contains 'get' and description states it 'Returns all tokens that can be received' — a pure query operation with no side effects. Uses public endpoints, returns informational data about available swap targets.
Attacks that exploit this kind of access
The rule that runs bitflow_get_swap_targets 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_swap_targets, this is the rule to start with:
bitflow_get_swap_targets 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_swap_targets call is checked against it from then on.
Questions about bitflow_get_swap_targets
Get possible swap target tokens for a given input token on Bitflow. Returns all tokens that can be received when swapping from the specified token. 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_swap_targets: 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_swap_targets 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_swap_targets 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_swap_targets. 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_swap_targets 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