hyperliquid_cancel_order
Signs and cancels an open Hyperliquid order for a coin enabled in the WebUI policy.
This record as markdown: /tools/awesome-base-mcp/hyperliquid-cancel-order.md
What hyperliquid_cancel_order does on Awesome Base
AI agents call hyperliquid_cancel_order to permanently remove resources in Awesome Base, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why hyperliquid_cancel_order is rated Critical
Canceling orders permanently removes open positions with real financial consequences that cannot be undone.
From the tool's definition cancels an open Hyperliquid order; irreversible financial action
Attacks that exploit this kind of access
The rule that runs hyperliquid_cancel_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Awesome Base, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hyperliquid_cancel_order, this is the rule to start with:
hyperliquid_cancel_order is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Awesome Base, apply this rule, and every hyperliquid_cancel_order call is checked against it from then on.
Questions about hyperliquid_cancel_order
Signs and cancels an open Hyperliquid order for a coin enabled in the WebUI policy. It is categorised as a Destructive tool in the Awesome Base MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Awesome Base MCP server in PolicyLayer and add a rule for hyperliquid_cancel_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 Awesome Base. Nothing to install.
hyperliquid_cancel_order 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 hyperliquid_cancel_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.
Set action: deny in the PolicyLayer policy for hyperliquid_cancel_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.
hyperliquid_cancel_order is provided by the Awesome Base MCP server (B5-Software/awesome-base-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Awesome Base, and thousands of servers like it.
Across the catalogue