hl_set_margin_mode
Switch between Cross and Isolated margin mode on Hyperliquid
This record as markdown: /tools/minhoyoo-iotrust-waiaas/hl-set-margin-mode.md
What hl_set_margin_mode does on Waiaas
AI agents use hl_set_margin_mode to commit financial operations through Waiaas, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why hl_set_margin_mode is rated Critical
Changing margin mode on a perpetuals exchange (Hyperliquid) directly affects how margin is allocated across positions. Switching from Isolated to Cross can expose the entire account balance to liquidation risk, or vice versa. This is a financial configuration change with significant implications for trading positions and potential losses, making it a Financial category tool with high severity.
From the tool's definition Switch between Cross and Isolated margin mode on Hyperliquid
Attacks that exploit this kind of access
The rule that runs hl_set_margin_mode 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_set_margin_mode, this is the rule to start with:
Any call to hl_set_margin_mode 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_set_margin_mode call is checked against it from then on.
Questions about hl_set_margin_mode
Switch between Cross and Isolated margin mode on Hyperliquid. 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_set_margin_mode: 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_set_margin_mode 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_set_margin_mode 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_set_margin_mode. 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_set_margin_mode 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