hyperliquid.markets.orderbook

Get L2 order book depth for a perpetual pair on Hyperliquid

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hyperliquid.markets.orderbook.md

WHAT IT DOES

What hyperliquid.markets.orderbook does on Apibase

AI agents call hyperliquid.markets.orderbook to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`coin`	string	Yes	Coin symbol (e.g. BTC, ETH)
`mantissa`	integer	—	Mantissa for price rounding
`n_sig_figs`	integer	—	Number of significant figures for price levels

Parameters from the server's own tool schema.

RISK

Why hyperliquid.markets.orderbook is rated Low

Retrieves market data without executing trades or modifying state.

From the tool's definition Get L2 order book depth for a perpetual pair

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hyperliquid.markets.orderbook safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hyperliquid.markets.orderbook, this is the rule to start with:

hyperliquid.markets.orderbook Allowed

hyperliquid.markets.orderbook is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hyperliquid.markets.orderbook": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every hyperliquid.markets.orderbook call is checked against it from then on.

FAQ

Questions about hyperliquid.markets.orderbook

What does the hyperliquid.markets.orderbook tool do? +

Get L2 order book depth for a perpetual pair on Hyperliquid. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does hyperliquid.markets.orderbook accept? +

hyperliquid.markets.orderbook accepts 3 parameters: coin, mantissa, n_sig_figs. Required: coin. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hyperliquid.markets.orderbook? +

Register the Apibase MCP server in PolicyLayer and add a rule for hyperliquid.markets.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 Apibase. Nothing to install.

What risk level is hyperliquid.markets.orderbook? +

hyperliquid.markets.orderbook is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hyperliquid.markets.orderbook? +

Yes. Add a rate_limit block to the hyperliquid.markets.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.

How do I block hyperliquid.markets.orderbook completely? +

Set action: deny in the PolicyLayer policy for hyperliquid.markets.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.

What MCP server provides hyperliquid.markets.orderbook? +

hyperliquid.markets.orderbook is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →