Get open orders from Hyperliquid exchange.
AI agents call get_open_orders 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 queries and retrieves existing order information from the Hyperliquid exchange. It does not create, modify, delete, or execute transactions. While it provides financial market data, the retrieval itself carries no financial risk—it is informational only. The low severity reflects that misuse would only expose account order information without enabling unauthorized trading or fund transfers.
From the tool's definition Tool name 'get_open_orders' and description 'Get open orders from Hyperliquid exchange' indicate a retrieval operation with no side effects. The verb 'get' and the action of retrieving order data without modification are characteristic of Read operations.
Attacks that exploit this kind of access
Get open orders from Hyperliquid exchange. 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_open_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. Nothing to install.
get_open_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_open_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_open_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_open_orders 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 →