AI agents call fetch_ohlcv to retrieve information from Crypto Multi-MCP Hub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
OHLCV data is purely historical price/volume information with no state-changing capability. Even in a trading context, fetching market data carries minimal risk—it cannot execute trades, transfer funds, or delete data. The tool's presence among sibling tools (amm_price, analyze_crypto_data, coin_info, compute_indicators) that are all read-based reinforces this classification.
From the tool's definition Tool name 'fetch_ohlcv' indicates retrieval of Open-High-Low-Close-Volume candlestick data, a standard financial time-series read operation. Despite empty description, the name directly implies data retrieval with no mutation or execution side effects.
Documented attack patterns abuse exactly the kind of access fetch_ohlcv gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crypto Multi-MCP Hub, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_ohlcv:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_ohlcv": {}
}
}fetch_ohlcv is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
fetch_ohlcv. It is categorised as a Read tool in the Crypto Multi-MCP Hub MCP Server, which means it retrieves data without modifying state.
Register the Crypto Multi-MCP Hub MCP server in PolicyLayer and add a rule for fetch_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 Crypto Multi-MCP Hub. Nothing to install.
fetch_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 fetch_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 fetch_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.
fetch_ohlcv is provided by the Crypto Multi-MCP Hub MCP server (pellenybe/crypto-mcp-server---by-corax-colab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crypto Multi-MCP Hub, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
48 Crypto Multi-MCP Hub tools catalogued and risk-classified — across an index of 43,000+ MCP servers.