crypto.dex-ohlcv
OHLCV candlesticks for a DEX pool (via GeckoTerminal, free/keyless). Pass network + pool address + timeframe (day/hour/minute) with optional aggregate (e.g. 4 = 4-hour) and limit. Returns time/open/high/low/close/volumeUsd bars for on-chain technical analysis. Pair with crypto.dex-pools / dex-tok...
This record as markdown: /tools/io-github-2s-io-mcp/crypto.dex-ohlcv.md
What crypto.dex-ohlcv does on Mcp
AI agents call crypto.dex-ohlcv to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crypto.dex-ohlcv is rated Low
This is a data retrieval tool that queries historical price and volume information. It has no side effects, does not modify data, does not execute code or transactions, and does not involve financial operations (it only reads market data, not moving funds or committing financial obligations). The 'pay-per-call' aspect of the server itself is a billing model, not a capability of this specific tool.
From the tool's definition Tool retrieves OHLCV candlestick data from GeckoTerminal for on-chain technical analysis. Description explicitly states it 'Returns time/open/high/low/close/volumeUsd bars' with no modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
The rule that runs crypto.dex-ohlcv safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto.dex-ohlcv, this is the rule to start with:
crypto.dex-ohlcv 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 Mcp, apply this rule, and every crypto.dex-ohlcv call is checked against it from then on.
Questions about crypto.dex-ohlcv
OHLCV candlesticks for a DEX pool (via GeckoTerminal, free/keyless). Pass network + pool address + timeframe (day/hour/minute) with optional aggregate (e.g. 4 = 4-hour) and limit. Returns time/open/high/low/close/volumeUsd bars for on-chain technical analysis. Pair with crypto.dex-pools / dex-token-pools to find a pool address. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for crypto.dex-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 Mcp. Nothing to install.
crypto.dex-ohlcv 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 crypto.dex-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.
Set action: deny in the PolicyLayer policy for crypto.dex-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.
crypto.dex-ohlcv is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue