calculate_put_call_ratio
AI agents call calculate_put_call_ratio 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 name suggests it calculates a put/call ratio, which is a standard market sentiment/analytics metric. Calculation tools of this nature are read-only operations that query options data and compute a ratio. The empty description lowers confidence, but context from sibling tools (all analytic/read operations) supports a Read classification. No evidence of write, execute, destructive, or financial operations.
From the tool's definition Tool name 'calculate_put_call_ratio' and empty description; sibling tools suggest analytics/read operations (analyze_*, analyze_risk, analyze_market_sentiment)
Attacks that exploit this kind of access
calculate_put_call_ratio. 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_put_call_ratio: 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_put_call_ratio 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_put_call_ratio 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_put_call_ratio. 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_put_call_ratio 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 →