Get stored daily end-of-day OHLCV candles for a stock, ETF, or crypto ticker. Use this for exact-return calculations, charts, and backtests after get_summary identifies a setup. Results are paginated; pass next_cursor back as cursor to continue. Equity and ETF bars are split-and-dividend adjusted...
AI agents call get_ohlcv to retrieve information from TickerDB without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | string | — | Inclusive end date (YYYY-MM-DD). |
limit | integer | — | Maximum candles to return (1-1000). Default: 100. |
order | string | — | Sort by candle date. Default: desc. |
start | string | — | Inclusive start date (YYYY-MM-DD). Lookback is limited by plan. |
cursor | string | — | Exclusive date cursor from next_cursor for pagination (YYYY-MM-DD). |
ticker | string | Yes | Ticker symbol, e.g. AAPL, BTCUSD, SPY |
Parameters from the server's own tool schema.
This is a straightforward data query tool that returns pre-computed historical market prices and volumes. It has no side effects, cannot modify data, and cannot execute external operations. The paginated results, credit cost, and data adjustment notes are operational details that do not change its fundamental Read category classification.
From the tool's definition Tool retrieves stored historical market data (OHLCV candles) for analysis and charting. Description explicitly states 'Get stored daily end-of-day OHLCV candles' and 'Use this for exact-return calculations, charts, and backtests' — pure data retrieval with no…
Attacks that exploit this kind of access
Get stored daily end-of-day OHLCV candles for a stock, ETF, or crypto ticker. Use this for exact-return calculations, charts, and backtests after get_summary identifies a setup. Results are paginated; pass next_cursor back as cursor to continue. Equity and ETF bars are split-and-dividend adjusted; crypto bars are unadjusted. Credit cost is 1 credit per 100 bars returned, rounded up, with a 1 credit minimum. It is categorised as a Read tool in the TickerDB MCP Server, which means it retrieves data without modifying state.
get_ohlcv accepts 6 parameters: end, limit, order, start, cursor, ticker. Required: ticker. The full parameter table on this page comes from the server's own tool schema.
Register the TickerDB MCP server in PolicyLayer and add a rule for get_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 TickerDB. Nothing to install.
get_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_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_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_ohlcv is provided by the TickerDB MCP server (tickerdb-mcp). 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 →