hl_create_sub_account
Create a new Hyperliquid sub-account
This record as markdown: /tools/minhoyoo-iotrust-waiaas/hl-create-sub-account.md
What hl_create_sub_account does on Waiaas
AI agents use hl_create_sub_account to commit financial operations through Waiaas, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why hl_create_sub_account is rated Critical
Creating a sub-account on Hyperliquid (a perpetuals/DeFi exchange) establishes a new financial account entity that can hold funds and execute trades. On a platform with perp trading and financial operations, sub-accounts are used to segregate funds and trading activity.
From the tool's definition Create a new Hyperliquid sub-account — on a server described as handling 'transfers, token management, DeFi (swap, lend, stake, bridge, perp)' with spending limits and financial operations
Attacks that exploit this kind of access
The rule that runs hl_create_sub_account 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_create_sub_account, this is the rule to start with:
Any call to hl_create_sub_account 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_create_sub_account call is checked against it from then on.
Questions about hl_create_sub_account
Create a new Hyperliquid sub-account. 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_create_sub_account: 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_create_sub_account 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_create_sub_account 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_create_sub_account. 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_create_sub_account 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