analyze_performance
AI agents call analyze_performance 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.
Despite the empty description, the tool name and server context strongly indicate this is an analytical function that computes performance metrics from portfolio data. It retrieves and processes information without creating, modifying, deleting, or executing external operations. The pattern of sibling analysis tools reinforces classification as Read.
From the tool's definition Tool name is 'analyze_performance' with empty description. Sibling tools on this server include 'analyze_bonds', 'analyze_risk', 'analyze_costs', 'analyze_dividend_income' — all analytics functions that fetch and compute on existing data without modification.
Attacks that exploit this kind of access
analyze_performance. 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 analyze_performance: 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.
analyze_performance 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 analyze_performance 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 analyze_performance. 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.
analyze_performance 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 →