hyperliquid.markets.data
Get market metadata and mid prices for all perpetual pairs on Hyperliquid
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hyperliquid.markets.data.md
What hyperliquid.markets.data does on Apibase
AI agents call hyperliquid.markets.data 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 | — | Specific coin symbol (e.g. BTC, ETH). Omit for all markets. |
Parameters from the server's own tool schema.
Why hyperliquid.markets.data is rated Low
Queries market data with no side effects; retrieves public information only.
From the tool's definition Get market metadata and mid prices for all perpetual pairs
Attacks that exploit this kind of access
The rule that runs hyperliquid.markets.data 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.data, this is the rule to start with:
hyperliquid.markets.data is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every hyperliquid.markets.data call is checked against it from then on.
Questions about hyperliquid.markets.data
Get market metadata and mid prices for all perpetual pairs on Hyperliquid. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
hyperliquid.markets.data accepts 1 parameter: coin. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for hyperliquid.markets.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 Apibase. Nothing to install.
hyperliquid.markets.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 hyperliquid.markets.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 hyperliquid.markets.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.
hyperliquid.markets.data 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.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue