Get historical market data
AI agents call get_historical_data to retrieve information from Interactive Brokers MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical market data without creating orders, modifying positions, executing trades, or deleting data. It is a passive read-only operation that returns data for analysis purposes. While the server manages financial accounts and can execute trades, this specific tool is limited to data retrieval with no side effects.
From the tool's definition Tool name 'get_historical_data' and description 'Get historical market data' indicate a retrieval operation with no modification or execution of trades. Retrieves past OHLCV or similar market data.
Attacks that exploit this kind of access
Get historical market data. It is categorised as a Read tool in the Interactive Brokers MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Interactive Brokers MCP Server MCP server in PolicyLayer and add a rule for get_historical_data: 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 Interactive Brokers MCP Server. Nothing to install.
get_historical_data 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 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. 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 is provided by the Interactive Brokers MCP Server MCP server (jinyiabc/ibkr-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 →