AI agents call get_user_staking_summary 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 'get_' prefix and naming pattern match other read-only query tools on the server (get_all_mids, get_candles_snapshot, get_user_fees, etc.). Staking summaries are informational data queries with no side effects. Confidence is slightly reduced due to empty description, but the tool name and broader context strongly indicate read-only behavior.
From the tool's definition Tool name 'get_user_staking_summary' indicates a retrieval operation. Description is empty, but context from sibling tools (all prefixed with 'get_') and the Hyperliquid exchange domain confirms this is a query tool that retrieves staking summary data without…
Documented attack patterns abuse exactly the kind of access get_user_staking_summary 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_staking_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_staking_summary": {}
}
}get_user_staking_summary 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_staking_summary. 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_staking_summary: 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_staking_summary 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_staking_summary 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_staking_summary. 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_staking_summary 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.