New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

bitflow_cancel_keeper_order

Cancel keeper order using official SDK

SERVERStacks AI MCP Server SOURCEstack-ai-mcp/stacks-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/bitflow-cancel-keeper-order.md

What bitflow_cancel_keeper_order does on Stacks AI MCP Server

AI agents call bitflow_cancel_keeper_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_keeper_order is rated Critical

Canceling a keeper order is a destructive action that irreversibly deletes an active order from the blockchain. This cannot be recovered or undone. While it may appear similar to Write operations, cancellation is fundamentally irreversible and affects financial positions.

From the tool's definition Tool name contains 'cancel' which is an irreversible action. In the context of a DeFi trading platform (Bitflow is a DEX on Stacks), canceling an order permanently removes it from the order book and cannot be undone without creating a new order.

Questions about bitflow_cancel_keeper_order

What does the bitflow_cancel_keeper_order tool do? +

Cancel keeper 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.

How do I enforce a policy on bitflow_cancel_keeper_order? +

Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for bitflow_cancel_keeper_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.

What risk level is bitflow_cancel_keeper_order? +

bitflow_cancel_keeper_order is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit bitflow_cancel_keeper_order? +

Yes. Add a rate_limit block to the bitflow_cancel_keeper_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.

How do I block bitflow_cancel_keeper_order completely? +

Set action: deny in the PolicyLayer policy for bitflow_cancel_keeper_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.

What MCP server provides bitflow_cancel_keeper_order? +

bitflow_cancel_keeper_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Stacks AI MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.