get_position_history
AI agents call get_position_history to retrieve information from IB Analytics 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 historical position information from Interactive Brokers portfolios—a read operation with no side effects. Even if misconfigured by an agent, it only exposes existing financial data rather than executing trades, modifying accounts, or deleting information. The risk is low unless sensitive position data itself is sensitive (which would be an organizational concern rather than a tool risk).
From the tool's definition Tool name 'get_position_history' indicates retrieval of historical position data. The server context describes 'automated data fetching and multi-dimensional analytics,' and sibling tools like 'analyze_*' are clearly analytical (read-only).
Attacks that exploit this kind of access
get_position_history. It is categorised as a Read tool in the IB Analytics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IB Analytics MCP Server MCP server in PolicyLayer and add a rule for get_position_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 IB Analytics MCP Server. Nothing to install.
get_position_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 get_position_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 get_position_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.
get_position_history is provided by the IB Analytics MCP Server MCP server (knishioka/ib-sec-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 →