Low Risk

dexPairsOhlcvHistorical

Returns historical OHLCV data along with market cap for any spot pairs using time interval parameters.

How to control dexPairsOhlcvHistorical ↓

AI agents call dexPairsOhlcvHistorical to retrieve information from CoinMarketCap MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves cryptocurrency market data (historical price and volume information) without side effects. It is a pure query operation that reads and returns existing data based on time interval parameters. There is no capability to execute code, modify data, delete records, or move funds.

From the tool's definition Tool returns historical OHLCV (Open, High, Low, Close, Volume) data and market cap for spot pairs. The verb 'Returns' and the word 'historical' indicate data retrieval with no modification capability.

Documented attack patterns abuse exactly the kind of access dexPairsOhlcvHistorical gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and CoinMarketCap MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for dexPairsOhlcvHistorical:

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

dexPairsOhlcvHistorical is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register CoinMarketCap MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the dexPairsOhlcvHistorical tool do? +

Returns historical OHLCV data along with market cap for any spot pairs using time interval parameters. It is categorised as a Read tool in the CoinMarketCap MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dexPairsOhlcvHistorical? +

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

What risk level is dexPairsOhlcvHistorical? +

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

Can I rate-limit dexPairsOhlcvHistorical? +

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

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

dexPairsOhlcvHistorical is provided by the CoinMarketCap MCP server (shinzo-labs/coinmarketcap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CoinMarketCap MCP tool call.

Deterministic rules across all 51 CoinMarketCap MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

51 CoinMarketCap MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.