Get account equity on Hyperliquid
AI agents call hl_get_balance to retrieve information from YOSO Agent SDK MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account equity information from Hyperliquid, a read-only operation with no side effects. While it accesses financial data, it does not move money, create obligations, or modify state. The low severity reflects that querying balance information poses minimal risk even if misused by an agent—it merely exposes existing account data rather than enabling transactions or destructive actions.
From the tool's definition Tool name 'hl_get_balance' and description 'Get account equity on Hyperliquid' indicate a query operation that retrieves financial account data without modifying it.
Attacks that exploit this kind of access
Get account equity on Hyperliquid. It is categorised as a Read tool in the YOSO Agent SDK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YOSO Agent SDK MCP Server MCP server in PolicyLayer and add a rule for hl_get_balance: 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 YOSO Agent SDK MCP Server. Nothing to install.
hl_get_balance is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hl_get_balance 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_get_balance. 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_get_balance is provided by the YOSO Agent SDK MCP Server MCP server (yosoagents/agent-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →