get_asset_contexts
AI agents call get_asset_contexts to retrieve information from Hyperliquid MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves asset context information from the Hyperliquid exchange. Despite the empty description limiting certainty, the naming convention and sibling context strongly suggest a query/retrieval operation with no side effects. No evidence suggests data creation, modification, deletion, code execution, or financial transactions. Classification as Read is appropriate for a market data retrieval tool.
From the tool's definition Tool name 'get_asset_contexts' follows the 'get_' prefix pattern consistent with other read-only tools on the server (get_candles, get_funding_rates, get_historical_orders, get_l2_orderbook, get_open_orders).
Attacks that exploit this kind of access
get_asset_contexts. It is categorised as a Read tool in the Hyperliquid MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hyperliquid MCP Server MCP server in PolicyLayer and add a rule for get_asset_contexts: 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 MCP Server. Nothing to install.
get_asset_contexts 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_asset_contexts 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_asset_contexts. 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_asset_contexts is provided by the Hyperliquid MCP Server MCP server (jhonatanpinheiro/hyperliquid-mcp-server). 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 →