hyperliquid_transfer
Signs and moves USDC between the Hyperliquid spot and perpetual accounts with the local Agent key, subject to the WebUI execution policy.
This record as markdown: /tools/awesome-base-mcp/hyperliquid-transfer.md
What hyperliquid_transfer does on Awesome Base
AI agents use hyperliquid_transfer to commit financial operations through Awesome Base, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why hyperliquid_transfer is rated Critical
Transfers USDC funds between accounts, committing financial obligations and moving money directly.
From the tool's definition Signs and moves USDC between accounts with Agent key
Attacks that exploit this kind of access
The rule that runs hyperliquid_transfer 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_transfer, this is the rule to start with:
Any call to hyperliquid_transfer is blocked until a human approves 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_transfer call is checked against it from then on.
Questions about hyperliquid_transfer
Signs and moves USDC between the Hyperliquid spot and perpetual accounts with the local Agent key, subject to the WebUI execution policy. It is categorised as a Financial tool in the Awesome Base MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Awesome Base MCP server in PolicyLayer and add a rule for hyperliquid_transfer: 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_transfer 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 hyperliquid_transfer 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_transfer. 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_transfer 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