calculate_metric
AI agents call calculate_metric 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 empty description, classification relies on context. The server is an analytics platform, and sibling tools are primarily Read-category analysis functions. A 'calculate_metric' tool most likely retrieves or computes metrics from existing portfolio data without modifying it. However, confidence is moderate (0.65) due to the lack of explicit description.
From the tool's definition Tool name is 'calculate_metric' with empty description. Sibling tools on the server include analysis functions (analyze_bonds, analyze_performance, analyze_risk) suggesting this tool performs computations on existing portfolio data rather than modifications.
Attacks that exploit this kind of access
calculate_metric. 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 calculate_metric: 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.
calculate_metric 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 calculate_metric 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 calculate_metric. 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.
calculate_metric 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 →