compare_with_benchmark
AI agents call compare_with_benchmark 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 appears to retrieve and compare portfolio performance data against benchmarks—a read-only analytical operation with no side effects. While the empty description reduces confidence slightly, the context of an analytics server and the verb 'compare' (not 'execute', 'modify', or 'delete') indicates data retrieval and calculation. The blast radius of misuse is low since no data is created, modified, or deleted.
From the tool's definition Tool name is 'compare_with_benchmark' which indicates a comparison/analysis operation. Server context shows it's part of IB Analytics MCP providing 'comprehensive analysis' and 'rich reporting capabilities'.
Attacks that exploit this kind of access
compare_with_benchmark. 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_with_benchmark: 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_with_benchmark 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_with_benchmark 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_with_benchmark. 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_with_benchmark 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 →