Low Risk

hyperliquid_get_spot_markets

Use this when you need live spot market data from Hyperliquid DEX: prices, 24h volume, and trading activity for all spot pairs. Returns merged token metadata + real-time market context for every active spot market. Returns for each market: 1. name: token name (e.g. "PURR/USDC") 2. coin: base toke...

Risk signalsBulk/mass operation — affects multiple targets

Part of the Hyperliquid Spot API server.

hyperliquid_get_spot_markets is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE HYPERLIQUID SPOT API →

Free to start. No card required.

AI agents call hyperliquid_get_spot_markets to retrieve information from Hyperliquid Spot API without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though hyperliquid_get_spot_markets only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "hyperliquid_get_spot_markets": {}
  }
}

See the full Hyperliquid Spot API policy for all 3 tools.

Get this rule live on your own Hyperliquid Spot API server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY HYPERLIQUID SPOT API →

These attack patterns abuse exactly the kind of access hyperliquid_get_spot_markets gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so hyperliquid_get_spot_markets only ever does what you allow.

SECURE HYPERLIQUID SPOT API →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the hyperliquid_get_spot_markets tool do? +

Use this when you need live spot market data from Hyperliquid DEX: prices, 24h volume, and trading activity for all spot pairs. Returns merged token metadata + real-time market context for every active spot market. Returns for each market: 1. name: token name (e.g. "PURR/USDC") 2. coin: base token symbol 3. tokenId: unique token identifier 4. markPx: current mark/mid price in USDC 5. midPx: mid price between best bid and ask 6. prevDayPx: previous day closing price 7. dayNtlVlm: 24h notional volume in USDC 8. change24h: percentage price change over 24 hours Sortable by: "volume" (default, highest 24h volume first), "change" (biggest movers first), "name" (alphabetical). Example output: { markets: [{ name: "PURR/USDC", markPx: "0.0234", dayNtlVlm: "1250000", change24h: 5.32 }], count: 120 } Use this to find trending spot tokens, check current prices, or scan for high-volume trading opportunities on Hyperliquid. Do NOT use for perps/futures markets -- use hyperliquid_get_perp_markets instead. Do NOT use for CoinGecko prices -- use token_get_price instead. Do NOT use for funding rates -- use hyperliquid_get_funding_rates instead. Do NOT use for historical OHLCV candles -- use token_get_ohlcv instead.. It is categorised as a Read tool in the Hyperliquid Spot API MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hyperliquid_get_spot_markets? +

Register the Hyperliquid Spot API MCP server in PolicyLayer and add a rule for hyperliquid_get_spot_markets: 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 Spot API. Nothing to install.

What risk level is hyperliquid_get_spot_markets? +

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

Can I rate-limit hyperliquid_get_spot_markets? +

Yes. Add a rate_limit block to the hyperliquid_get_spot_markets 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_get_spot_markets completely? +

Set action: deny in the PolicyLayer policy for hyperliquid_get_spot_markets. 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_get_spot_markets? +

hyperliquid_get_spot_markets is provided by the Hyperliquid Spot API MCP server (https://hl-spot.api.klymax402.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Hyperliquid Spot API tool call.

Deterministic rules across all 3 Hyperliquid Spot API tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.