bitflow_cancel_group_order
Cancel group order using official SDK
This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/bitflow-cancel-group-order.md
What bitflow_cancel_group_order does on Stacks AI MCP Server
AI agents call bitflow_cancel_group_order to permanently remove resources in Stacks AI MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why bitflow_cancel_group_order is rated Critical
Cancelling a group order is an irreversible action that destroys the order's active state and cannot be undone without creating a new order. In the context of DeFi trading on Stacks, this represents a destructive operation with financial implications. While it doesn't move funds directly (which would be Financial), it permanently modifies blockchain state by eliminating an order commitment.
From the tool's definition Tool name includes 'cancel' which is an irreversible operation that removes or nullifies an existing group order. The description states it 'cancel[s] group order' using the official SDK, indicating a destructive action on blockchain state.
Attacks that exploit this kind of access
The rule that runs bitflow_cancel_group_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stacks AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bitflow_cancel_group_order, this is the rule to start with:
bitflow_cancel_group_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 Stacks AI MCP Server, apply this rule, and every bitflow_cancel_group_order call is checked against it from then on.
Questions about bitflow_cancel_group_order
Cancel group order using official SDK. It is categorised as a Destructive tool in the Stacks AI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for bitflow_cancel_group_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 Stacks AI MCP Server. Nothing to install.
bitflow_cancel_group_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_group_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_group_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_group_order is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stacks AI MCP Server, and thousands of servers like it.
Across the catalogue