Low Risk

hyperliquid_list_spot_tokens

Use this when you need to list or search spot tokens available on Hyperliquid L1 DEX. Returns all 454 spot tokens with full metadata including token name, symbol, tokenId, index, decimals, and wei conversion factors. Returns for each token: 1. name: token display name (e.g. "PURR", "HFUN") 2. tok...

Part of the Hyperliquid Spot API server.

hyperliquid_list_spot_tokens 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_list_spot_tokens 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_list_spot_tokens 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_list_spot_tokens": {}
  }
}

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_list_spot_tokens 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_list_spot_tokens 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_list_spot_tokens tool do? +

Use this when you need to list or search spot tokens available on Hyperliquid L1 DEX. Returns all 454 spot tokens with full metadata including token name, symbol, tokenId, index, decimals, and wei conversion factors. Returns for each token: 1. name: token display name (e.g. "PURR", "HFUN") 2. tokenId: unique hex token identifier on Hyperliquid 3. index: integer index in the spot meta registry 4. decimals: token decimal precision (szDecimals) 5. weiDecimals: wei-level decimal precision for raw amounts Optional filter: pass "search" to filter tokens by name/symbol substring match (case-insensitive). Returns all tokens if no search term provided. Example output: { tokens: [{ name: "PURR", tokenId: "0xc4bf3f...", index: 1, decimals: 0, weiDecimals: 8 }], count: 454 } Use this to discover which spot tokens exist on Hyperliquid before querying prices or balances. Essential for building trading interfaces or token lookups. Do NOT use for perps/futures data -- use hyperliquid_get_perp_markets instead. Do NOT use for token prices on CEX/CoinGecko -- use token_get_price instead. Do NOT use for wallet portfolio across chains -- use wallet_get_portfolio instead. Do NOT use for Hyperliquid vault data -- use hyperliquid_get_vaults 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_list_spot_tokens? +

Register the Hyperliquid Spot API MCP server in PolicyLayer and add a rule for hyperliquid_list_spot_tokens: 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_list_spot_tokens? +

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

Can I rate-limit hyperliquid_list_spot_tokens? +

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

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

hyperliquid_list_spot_tokens 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.