[Cancel Orders / Bulk Cancel] 複数の注文を一括キャンセル（最大30件）。キャンセル後の注文情報を返す。Private API。
AI agents call cancel_orders to permanently remove resources in Bitbank Lab — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Canceling orders is a destructive action that cannot be undone—once canceled, the order state change is permanent and affects trading positions. This impacts financial obligations and market exposure. Although not a direct money transfer, it is destructive in nature (order cancellation cannot be reversed) and operates on financial instruments.
From the tool's definition Tool name 'cancel_orders' with description indicating bulk cancellation of orders (up to 30 at once). Japanese text '複数の注文を一括キャンセル' translates to 'bulk cancel multiple orders'. This is irreversible cancellation of financial orders.
Attacks that exploit this kind of access
[Cancel Orders / Bulk Cancel] 複数の注文を一括キャンセル（最大30件）。キャンセル後の注文情報を返す。Private API。. It is categorised as a Destructive tool in the Bitbank Lab MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bitbank Lab MCP server in PolicyLayer and add a rule for cancel_orders: 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 Bitbank Lab. Nothing to install.
cancel_orders 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 cancel_orders 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 cancel_orders. 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.
cancel_orders is provided by the Bitbank Lab MCP server (tjackiet/bitbank-genesis-mcp-server-http-archive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →