bitflow_cancel_order
Cancel a Bitflow Keeper order. Cancels a pending order before execution. 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-cancel-order.md
What bitflow_cancel_order does on Aibtc
AI agents call bitflow_cancel_order to permanently remove resources in Aibtc, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why bitflow_cancel_order is rated Critical
Cancelling an order is an irreversible action — once cancelled, the pending order cannot be reinstated. This is a destructive operation that permanently terminates a financial order. While it prevents a financial transaction from completing, the cancellation itself is irreversible, placing it in the Destructive category.
From the tool's definition Cancel a Bitflow Keeper order. Cancels a pending order before execution.
Attacks that exploit this kind of access
The rule that runs bitflow_cancel_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_cancel_order, this is the rule to start with:
bitflow_cancel_order is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every bitflow_cancel_order call is checked against it from then on.
Questions about bitflow_cancel_order
Cancel a Bitflow Keeper order. Cancels a pending order before execution. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet. It is categorised as a Destructive tool in the Aibtc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aibtc MCP server in PolicyLayer and add a rule for bitflow_cancel_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_cancel_order is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bitflow_cancel_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_cancel_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_cancel_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.
Across the catalogue