Get spot account state and balances from Hyperliquid.
AI agents call get_spot_user_state to retrieve information from Hyperliquid without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account state and balance information without altering any data, triggering external operations, or moving funds. It is purely informational. While the data accessed is sensitive (account balances), the tool itself performs no destructive or consequential action.
From the tool's definition Tool name 'get_spot_user_state' and description 'Get spot account state and balances from Hyperliquid' indicate data retrieval with no modifications. The verb 'Get' and lack of any write/delete/execute/financial action language confirm read-only behavior.
Attacks that exploit this kind of access
Get spot account state and balances from Hyperliquid. It is categorised as a Read tool in the Hyperliquid MCP Server, which means it retrieves data without modifying state.
Register the Hyperliquid MCP server in PolicyLayer and add a rule for get_spot_user_state: 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 Hyperliquid. Nothing to install.
get_spot_user_state 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 get_spot_user_state 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 get_spot_user_state. 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.
get_spot_user_state is provided by the Hyperliquid MCP server (midodimori/hyperliquid-mcp). 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 →