AI agents call get_user_state to retrieve information from Hyperliquid Info without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming convention ('get_') and context of sibling tools on a financial data API server (Hyperliquid exchange info) strongly suggest this retrieves user state information rather than modifying it. No description provided, but the consistent pattern of read-only query tools on this server reduces confidence only moderately.
From the tool's definition Tool name 'get_user_state' combined with sibling tools that are all read-only queries (get_all_mids, get_candles_snapshot, get_coin_funding_history, get_l2_snapshot, get_perp_metadata, get_spot_metadata, get_user_fees, get_user_funding_history,…
Documented attack patterns abuse exactly the kind of access get_user_state gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hyperliquid Info, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user_state:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_state": {}
}
}get_user_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_user_state. It is categorised as a Read tool in the Hyperliquid Info MCP Server, which means it retrieves data without modifying state.
Register the Hyperliquid Info MCP server in PolicyLayer and add a rule for get_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 Info. Nothing to install.
get_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_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_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_user_state is provided by the Hyperliquid Info MCP server (kukapay/hyperliquid-info-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Hyperliquid Info, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Hyperliquid Info tools catalogued and risk-classified — across an index of 43,000+ MCP servers.