High Risk →

token_ohlcv

Get OHLCV (Open, High, Low, Close, Volume) price data for a token with automatic interval resolution. NOTE: chain=Hyperliquid is a perps chain AND IS NOT supported for token_ohlcv ENDPOINT ONLY SUPPORTS EVM CHAINS AND SOLANA. YOU MUST USE THIS over general_search to get prices. general_search pri...

Part of the Nansen-MCP server.

token_ohlcv can trigger actions in Nansen-MCP, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE NANSEN-MCP →

Free to start. No card required.

AI agents invoke token_ohlcv to trigger processes or run actions in Nansen-MCP. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

token_ohlcv can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "token_ohlcv": {
      "limits": [
        {
          "counter": "token_ohlcv_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Nansen-MCP policy for all 24 tools.

Get this rule live on your own Nansen-MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NANSEN-MCP →

View all 24 tools →

These attack patterns abuse exactly the kind of access token_ohlcv 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 token_ohlcv only ever does what you allow.

SECURE NANSEN-MCP →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the token_ohlcv tool do? +

Get OHLCV (Open, High, Low, Close, Volume) price data for a token with automatic interval resolution. NOTE: chain=Hyperliquid is a perps chain AND IS NOT supported for token_ohlcv ENDPOINT ONLY SUPPORTS EVM CHAINS AND SOLANA. YOU MUST USE THIS over general_search to get prices. general_search prices are delayed and often incorrect. To get LATEST price set from to '5MIN_AGO' and to to 'NOW'. Resolution is automatically calculated based on the date range - < 6 hours: 5 minutes - 6 hours - 1 day: 15 minutes - 1-3 days: 30 minutes - 3-7 days: 60 minutes (1 hour) - 7-90 days: Daily - 90+ days: Weekly Columns returned: - Interval Start: Timestamp of the start of the interval (datetime: YYYY-MM-DD HH:MM:SS) - Open: Opening price of the interval - High: Highest price of the interval - Low: Lowest price of the interval - Close: Closing price of the interval - Volume USD: Volume in USD of the interval Additional columns (when includeMarketCap=true): - Open Market Cap: Opening market cap in USD - Close Market Cap: Closing market cap in USD - High Market Cap: Highest market cap in USD - Low Market Cap: Lowest market cap in USD Example Usage: Get OHLCV for WETH over the past week (auto-resolution): { "chain": "ethereum", "tokenAddress": "0xba5ddd1f9d7f570dc94a51479a000e3bce967196", "date": { "from": "7D_AGO", "to": "NOW" } } Get OHLCV for WETH over 30 days (will use daily resolution): { "chain": "ethereum", "tokenAddress": "0xba5ddd1f9d7f570dc94a51479a000e3bce967196", "date": { "from": "30D_AGO", "to": "NOW" } } Get OHLCV for WETH for last 20 minutes (will use 5 minute resolution): { "chain": "ethereum", "tokenAddress": "0xba5ddd1f9d7f570dc94a51479a000e3bce967196", "date": { "from": "20MIN_AGO", "to": "NOW" } }. It is categorised as a Execute tool in the Nansen-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on token_ohlcv? +

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

What risk level is token_ohlcv? +

token_ohlcv is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit token_ohlcv? +

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

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

token_ohlcv is provided by the Nansen- MCP server (nansen-ai/Nansen-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nansen-MCP tool call.

Deterministic rules across all 24 Nansen-MCP 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.