Get the orderbook (bids and asks) for a perpetual market
AI agents call get_orderbook 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 fetches real-time market data (bid/ask orders) from the exchange. It is a read-only operation that queries existing data without creating, modifying, deleting, or executing any actions. The tool cannot affect positions, balances, or orders. Even in a financial context, querying public market data carries minimal risk compared to order placement or position management tools on this server.
From the tool's definition 'Get the orderbook (bids and asks) for a perpetual market' - a query operation that retrieves market data with no side effects or ability to modify state.
Attacks that exploit this kind of access
Get the orderbook (bids and asks) for a perpetual market. 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_orderbook: 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_orderbook 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_orderbook 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_orderbook. 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_orderbook is provided by the Hyperliquid MCP Server MCP server (samklein952-hub/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 →