Cancel one or all orders for a market on Hyperliquid
AI agents call hl_cancel_order to permanently remove resources in Waiaas — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While this appears transactional, order cancellation is destructive in nature because it permanently removes an active market instruction. Unlike reversible operations (write) that can be modified or undone, a cancelled order cannot be restored to its pre-cancellation state.
From the tool's definition Tool cancels orders on Hyperliquid, which irreversibly terminates active trading positions. The action "cancel" combined with "order" on a financial exchange removes a previously submitted instruction that cannot be restored—the cancelled order state is…
Documented attack patterns abuse exactly the kind of access hl_cancel_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Waiaas, and nothing reaches the server without passing your rules. This is the rule we recommend for hl_cancel_order:
{
"version": "1",
"default": "deny",
"hide": [
"hl_cancel_order"
]
}hl_cancel_order disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Cancel one or all orders for a market on Hyperliquid. It is categorised as a Destructive tool in the Waiaas MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Waiaas MCP server in PolicyLayer and add a rule for hl_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 Waiaas. Nothing to install.
hl_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 hl_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 hl_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.
hl_cancel_order is provided by the Waiaas MCP server (minhoyoo-iotrust/waiaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Waiaas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
126 Waiaas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.