Get historical price data with technical indicators
AI agents call get_historical_data_v2 to retrieve information from StockFlow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical stock price data and calculates technical indicators—purely read-only operations with no side effects. Users cannot execute trades, modify data, or trigger financial transactions. The blast radius is minimal; worst case, an AI agent receives outdated or misinterpreted historical data, which is low-impact.
From the tool's definition Tool name 'get_historical_data' and description 'Get historical price data with technical indicators' indicate data retrieval only. No modification, deletion, or execution capability is mentioned.
Documented attack patterns abuse exactly the kind of access get_historical_data_v2 gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and StockFlow MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_historical_data_v2:
{
"version": "1",
"default": "deny",
"tools": {
"get_historical_data_v2": {}
}
}get_historical_data_v2 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 price data with technical indicators. It is categorised as a Read tool in the StockFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the StockFlow MCP Server MCP server in PolicyLayer and add a rule for get_historical_data_v2: 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 StockFlow MCP Server. Nothing to install.
get_historical_data_v2 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_historical_data_v2 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_historical_data_v2. 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_historical_data_v2 is provided by the StockFlow MCP Server MCP server (twolven/mcp-stockflow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from StockFlow MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 StockFlow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.