yahoo_finance_ticker_history
Yahoo Finance historical prices. Returns normalized OHLCV points for a symbol. Use either period or start/end.
This record as markdown: /tools/crawlora-mcp/yahoo-finance-ticker-history.md
What yahoo_finance_ticker_history does on Crawlora
AI agents invoke yahoo_finance_ticker_history to trigger actions in Crawlora. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | string | — | Unix seconds, RFC3339, or YYYY-MM-DD |
start | string | — | Unix seconds, RFC3339, or YYYY-MM-DD |
keepna | boolean | — | Keep fully empty chart rows |
period | string | — | Range such as 1d, 1mo, 1y, max |
symbol | string | Yes | Yahoo Finance symbol such as AAPL |
interval | string | — | Interval such as 1d, 1h, 5m |
rounding | boolean | — | Round prices to two decimals |
auto_adjust | boolean | — | Adjust OHLC prices with adjusted close |
back_adjust | boolean | — | Back-adjust OHLC prices while keeping close |
include_actions | boolean | — | Include dividends, splits, and capital gains |
include_prepost | boolean | — | Include pre/post market data |
Parameters from the server's own tool schema.
Why yahoo_finance_ticker_history is rated High
yahoo_finance_ticker_history triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs yahoo_finance_ticker_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For yahoo_finance_ticker_history, this is the rule to start with:
yahoo_finance_ticker_history stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every yahoo_finance_ticker_history call is checked against it from then on.
Questions about yahoo_finance_ticker_history
Yahoo Finance historical prices. Returns normalized OHLCV points for a symbol. Use either period or start/end. It is categorised as a Execute tool in the Crawlora MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
yahoo_finance_ticker_history accepts 11 parameters: end, start, keepna, period, symbol, interval, rounding, auto_adjust, back_adjust, include_actions, include_prepost. Required: symbol. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for yahoo_finance_ticker_history: 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 Crawlora. Nothing to install.
yahoo_finance_ticker_history is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the yahoo_finance_ticker_history 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 yahoo_finance_ticker_history. 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.
yahoo_finance_ticker_history is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
Across the catalogue