get_options_chain
AI agents call get_options_chain 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.
Options chain data retrieval is fundamentally a read operation—it queries and returns market or portfolio data without modifying state. However, severity is elevated to 'medium' rather than 'low' because: (1) options data could be used by an AI agent to make unauthorized trading recommendations or analyses, (2) the broader server context includes order placement capabilities (add_limit_order), creating potential for…
From the tool's definition Tool name 'get_options_chain' indicates retrieval of options chain data. Context from sibling tools shows this server performs 'analysis' and 'data fetching' of Interactive Brokers portfolios.
Attacks that exploit this kind of access
get_options_chain. 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_options_chain: 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_options_chain 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_options_chain 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_options_chain. 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_options_chain 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 →