Cancel multiple orders.
AI agents call cancelBatchOrders to permanently remove resources in Aster Finance MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Canceling multiple orders on a futures exchange is a destructive action that cannot be undone. Once canceled, orders are permanently removed and cannot be recovered. This action directly impacts open positions and trading strategies. The tool operates in a financial trading context where cancellations have real monetary consequences.
From the tool's definition Tool named 'cancelBatchOrders' with description 'Cancel multiple orders' on a cryptocurrency futures trading platform. Canceling orders is irreversible and immediately terminates active trading positions.
Attacks that exploit this kind of access
Cancel multiple orders. It is categorised as a Destructive tool in the Aster Finance MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aster Finance MCP Server MCP server in PolicyLayer and add a rule for cancelBatchOrders: 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 Aster Finance MCP Server. Nothing to install.
cancelBatchOrders 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 cancelBatchOrders 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 cancelBatchOrders. 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.
cancelBatchOrders is provided by the Aster Finance MCP Server MCP server (questflowai/aster-mcp-server). 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 →