Get historical OHLCV price data. Args: symbol: Ticker symbol period: Time period (1d, 5d, 1mo, 3mo, 6mo, 1y, 2y, 5y, 10y, ytd, max) interval: Data interval (1m, 2m, 5m, 15m, 30m, 60m, 90m, 1h, 1d, 5d, 1wk, 1mo)
AI agents call price_history to retrieve information from Trading Skills without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
price_history performs a read-only data retrieval operation. It fetches historical Open, High, Low, Close, Volume price information from financial markets. There is no capability to modify data, execute trades, delete information, or commit financial resources. The only risk is information disclosure, which is minimal since historical price data is publicly available.
From the tool's definition Tool description states 'Get historical OHLCV price data' with parameters for symbol, period, and interval.
Documented attack patterns abuse exactly the kind of access price_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trading Skills, and nothing reaches the server without passing your rules. This is the rule we recommend for price_history:
{
"version": "1",
"default": "deny",
"tools": {
"price_history": {}
}
}price_history 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 price data. Args: symbol: Ticker symbol period: Time period (1d, 5d, 1mo, 3mo, 6mo, 1y, 2y, 5y, 10y, ytd, max) interval: Data interval (1m, 2m, 5m, 15m, 30m, 60m, 90m, 1h, 1d, 5d, 1wk, 1mo). It is categorised as a Read tool in the Trading Skills MCP Server, which means it retrieves data without modifying state.
Register the Trading Skills MCP server in PolicyLayer and add a rule for price_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 Trading Skills. Nothing to install.
price_history 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 price_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 price_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.
price_history is provided by the Trading Skills MCP server (staskh/trading_skills). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 35 Trading Skills tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
35 Trading Skills tools catalogued and risk-classified — across an index of 42,500+ MCP servers.