Get historical OHLCV (candlestick) data for a trading pair
AI agents call get-historical-ohlcv to retrieve information from Cryptocurrency Market Data MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns historical market data. It does not create, modify, delete, or execute any operations. There are no financial transactions, no code execution, and no irreversible actions. The worst-case misuse would be excessive data requests, but no monetary loss or system compromise is possible. Classified as Read with low severity.
From the tool's definition Tool retrieves historical OHLCV candlestick data—a passive read operation that fetches market data without any side effects, creation, modification, deletion, or execution of commands.
Documented attack patterns abuse exactly the kind of access get-historical-ohlcv gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cryptocurrency Market Data MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-historical-ohlcv:
{
"version": "1",
"default": "deny",
"tools": {
"get-historical-ohlcv": {}
}
} get-historical-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.
Get historical OHLCV (candlestick) data for a trading pair. It is categorised as a Read tool in the Cryptocurrency Market Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cryptocurrency Market Data MCP Server MCP server in PolicyLayer and add a rule for get-historical-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 Cryptocurrency Market Data MCP Server. Nothing to install.
get-historical-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 get-historical-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 get-historical-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.
get-historical-ohlcv is provided by the Cryptocurrency Market Data MCP Server MCP server (nayshins/mcp-server-ccxt). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cryptocurrency Market Data MCP Server, 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.
7 Cryptocurrency Market Data MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.