compare_portfolio_snapshots
AI agents call compare_portfolio_snapshots 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.
The tool appears to compare portfolio snapshots, which is fundamentally a read operation that retrieves and analyzes existing portfolio data without creating, modifying, or deleting data. While the lack of description reduces confidence slightly, the name and context within a broader analytics platform point clearly to a Read classification.
From the tool's definition Tool name 'compare_portfolio_snapshots' indicates retrieval and comparison of portfolio state data. No description provided, but the naming convention and sibling tools (analyze_*) suggest data analysis without modification.
Attacks that exploit this kind of access
compare_portfolio_snapshots. 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 compare_portfolio_snapshots: 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.
compare_portfolio_snapshots 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 compare_portfolio_snapshots 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 compare_portfolio_snapshots. 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.
compare_portfolio_snapshots 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 →