evaluate_position
AI agents call evaluate_position 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.
Given the server's focus on analytics and reporting, and the naming convention matching other analytical sibling tools, 'evaluate_position' most likely retrieves and analyzes data about a portfolio position without side effects. However, confidence is moderate (0.75) rather than high due to empty description—it could theoretically place or modify orders, but this is unlikely given the analytical context.
From the tool's definition Tool name 'evaluate_position' suggests analysis/assessment of existing portfolio holdings. Sibling tools include many 'analyze_*' functions (analyze_performance, analyze_risk, analyze_bonds, etc.) which are clearly Read operations.
Attacks that exploit this kind of access
evaluate_position. 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 evaluate_position: 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.
evaluate_position 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 evaluate_position 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 evaluate_position. 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.
evaluate_position 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 →