bitflow_create_order
Create an automated swap order via Bitflow Keeper. Creates a pending order that will be executed by the Keeper service. 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-create-order.md
What bitflow_create_order does on Aibtc
AI agents use bitflow_create_order to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why bitflow_create_order is rated Medium
The tool creates (writes) a new automated swap order, which is a reversible state change but commits a financial intent. While the order is 'pending' and could potentially be cancelled, the tool itself performs a Write action by creating the order object.
From the tool's definition Creates a pending order that will be executed by the Keeper service — this is a state-changing operation that creates a new financial order in a swap system.
Attacks that exploit this kind of access
The rule that runs bitflow_create_order 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_create_order, this is the rule to start with:
bitflow_create_order stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_create_order call is checked against it from then on.
Questions about bitflow_create_order
Create an automated swap order via Bitflow Keeper. Creates a pending order that will be executed by the Keeper service. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aibtc MCP server in PolicyLayer and add a rule for bitflow_create_order: 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_create_order is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bitflow_create_order 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_create_order. 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_create_order 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