Low Risk

historical_price_series

Fetch historical OHLCV price series for any ticker: stocks (AAPL, SAP.DE, 7203.T), ETFs, indices, commodities (GC=F for gold) or cryptocurrencies (BTC-USD). Returns a full date-indexed series of open/high/low/close/volume plus pre-computed statistics: total return, annualised return (CAGR), annua...

Part of the Mcp Knowledge server.

historical_price_series is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MCP KNOWLEDGE →

Free to start. No card required.

AI agents call historical_price_series to retrieve information from Mcp Knowledge without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though historical_price_series only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "historical_price_series": {}
  }
}

See the full Mcp Knowledge policy for all 271 tools.

Get this rule live on your own Mcp Knowledge server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCP KNOWLEDGE →

View all 271 tools →

These attack patterns abuse exactly the kind of access historical_price_series gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so historical_price_series only ever does what you allow.

SECURE MCP KNOWLEDGE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the historical_price_series tool do? +

Fetch historical OHLCV price series for any ticker: stocks (AAPL, SAP.DE, 7203.T), ETFs, indices, commodities (GC=F for gold) or cryptocurrencies (BTC-USD). Returns a full date-indexed series of open/high/low/close/volume plus pre-computed statistics: total return, annualised return (CAGR), annualised volatility, max drawdown and Sharpe estimate (rf=4%). Automatically detects crypto tickers (→ CoinGecko) vs traditional assets (→ Yahoo Finance primary, Stooq fallback). Adjusts for dividends and splits when adjusted=true (default). Use cases: backtesting, factor analysis, performance attribution, charting, financial modelling. Sources: Yahoo Finance, CoinGecko, Stooq. All keyless. Optional env: AICI_RESEARCH_PROXY_URL for Bright Data routing (lifts Yahoo 429), TWELVE_DATA_API_KEY for higher Twelve Data quota.. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on historical_price_series? +

Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for historical_price_series: 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 Knowledge. Nothing to install.

What risk level is historical_price_series? +

historical_price_series is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit historical_price_series? +

Yes. Add a rate_limit block to the historical_price_series 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.

How do I block historical_price_series completely? +

Set action: deny in the PolicyLayer policy for historical_price_series. 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.

What MCP server provides historical_price_series? +

historical_price_series is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Knowledge tool call.

Deterministic rules across all 271 Mcp Knowledge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.