Get OHLCV candlestick data for any crypto. Returns open, high, low, close for each period.
AI agents call candles to retrieve information from Mcp Market Data without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves market data without side effects. It performs a passive read of candlestick data, which is the core function of market data APIs. While the broader server handles financial markets, this specific tool does not move money, execute trades, or modify state—it only fetches historical OHLCV (open-high-low-close-volume) information.
From the tool's definition Tool description states 'Get OHLCV candlestick data' — a retrieval operation that returns historical price data (open, high, low, close). No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
Get OHLCV candlestick data for any crypto. Returns open, high, low, close for each period. It is categorised as a Read tool in the Mcp Market Data MCP Server, which means it retrieves data without modifying state.
Register the Mcp Market Data MCP server in PolicyLayer and add a rule for candles: 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 Market Data. Nothing to install.
candles 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 candles 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 candles. 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.
candles is provided by the Mcp Market Data MCP server (shipitandpray/mcp-market-data). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →