cancel_all_orders
AI agents call cancel_all_orders to permanently remove resources in Hyperliquid MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling all orders on a trading platform is an irreversible bulk action that removes all active trading positions/orders simultaneously. While it doesn't delete data permanently, mass-cancelling orders on a DEX cannot be undone and could cause significant financial disruption to an active trading strategy. The sibling tool 'cancel_order' confirms this is about order cancellation.
From the tool's definition Tool name 'cancel_all_orders' combined with sibling tool 'cancel_order' on a decentralized exchange trading server
Attacks that exploit this kind of access
cancel_all_orders. It is categorised as a Destructive tool in the Hyperliquid MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hyperliquid MCP Server MCP server in PolicyLayer and add a rule for cancel_all_orders: 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 Hyperliquid MCP Server. Nothing to install.
cancel_all_orders 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_all_orders 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_all_orders. 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_all_orders is provided by the Hyperliquid MCP Server MCP server (jhonatanpinheiro/hyperliquid-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 →