Get historical orders with their status.
AI agents call get_historical_orders 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.
This tool retrieves historical order data and their statuses from the Hyperliquid exchange. It performs no modifications, deletions, executions, or financial transactions. While the server context involves financial trading, this specific tool is purely informational—it queries past order records without triggering any market actions or fund movements.
From the tool's definition Tool name 'get_historical_orders' and description 'Get historical orders with their status' indicate a query/retrieval operation with no side effects. The verb 'get' and lack of any modification language confirm this is a read operation.
Attacks that exploit this kind of access
Get historical orders with their status. 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_historical_orders: 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_historical_orders 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_historical_orders 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_historical_orders. 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_historical_orders 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 →