add_order_batch
AI agents use add_order_batch to commit financial operations through Mcp Kraken — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Based on the server context (Kraken crypto exchange) and the tool name pattern matching 'add_order' (single) vs 'add_order_batch' (multiple), this tool almost certainly places multiple orders at once on the exchange, committing real financial obligations. Batch order placement amplifies blast radius significantly — a misuse could result in large unintended trades.
From the tool's definition Tool name 'add_order_batch' on a Kraken cryptocurrency exchange MCP server; sibling tools include 'add_order', 'cancel_order', 'cancel_order_batch', indicating this tool places multiple trading orders simultaneously.
Attacks that exploit this kind of access
add_order_batch. It is categorised as a Financial tool in the Mcp Kraken MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Kraken MCP server in PolicyLayer and add a rule for add_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.
add_order_batch is a Financial 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 add_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 add_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.
add_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 →