Cancel up to 50 orders in a single call.
AI agents call cancel_order_batch to permanently remove resources in Mcp Kraken — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call cancel_order_batch doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Kraken is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Cancel up to 50 orders in a single call. It is categorised as a Destructive tool in the Mcp Kraken MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Kraken MCP server in PolicyLayer and add a rule for cancel_order_batch: 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 Mcp Kraken. Nothing to install.
cancel_order_batch 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_order_batch 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_order_batch. 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_order_batch is provided by the Mcp Kraken MCP server (xavierbeheydt/mcp-kraken). 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 →