hl_close_position
Close a perpetual position on Hyperliquid (full or partial close)
This record as markdown: /tools/minhoyoo-iotrust-waiaas/hl-close-position.md
What hl_close_position does on Waiaas
AI agents use hl_close_position to commit financial operations through Waiaas, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why hl_close_position is rated Critical
Closing a perpetual futures position on Hyperliquid is a financial operation that executes a trade on a derivatives exchange, realizing gains or losses and releasing collateral. This directly involves financial transactions in crypto markets. Misuse could result in significant financial loss due to forced position closure at unfavorable prices or unintended liquidation triggers.
From the tool's definition Close a perpetual position on Hyperliquid (full or partial close)
Attacks that exploit this kind of access
The rule that runs hl_close_position safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Waiaas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hl_close_position, this is the rule to start with:
Any call to hl_close_position is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Waiaas, apply this rule, and every hl_close_position call is checked against it from then on.
Questions about hl_close_position
Close a perpetual position on Hyperliquid (full or partial close). It is categorised as a Financial tool in the Waiaas MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Waiaas MCP server in PolicyLayer and add a rule for hl_close_position: 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_close_position 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 hl_close_position 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_close_position. 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_close_position 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.
More on Waiaas, and thousands of servers like it.
Across the catalogue