Get historical candle/OHLCV data for a specific asset from Hyperliquid.
AI agents call get_candle_data 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 historical OHLCV (Open, High, Low, Close, Volume) candle data, which is a read-only operation that queries market data without side effects. It does not create, modify, delete, or execute any trading operations, nor does it commit financial obligations. The data returned is already settled historical information with no risk of unintended financial consequences from misuse.
From the tool's definition Tool name 'get_candle_data' and description 'Get historical candle/OHLCV data for a specific asset' indicates retrieval of historical market data with no modification or execution of trades.
Attacks that exploit this kind of access
Get historical candle/OHLCV data for a specific asset 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_candle_data: 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_candle_data 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_candle_data 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_candle_data. 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_candle_data 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 →