analyze_dividend_income
AI agents call analyze_dividend_income 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 appears designed to retrieve and analyze dividend income data from Interactive Brokers portfolios, consistent with the server's stated purpose of 'comprehensive analysis' and 'reporting capabilities.' Analysis tools in financial contexts typically query and present data without modifying portfolios or executing trades.
From the tool's definition Tool name 'analyze_dividend_income' and server description indicating 'analysis' and 'analytics' capabilities suggest data retrieval and reporting. No mutation or execution language present. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
analyze_dividend_income. 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_dividend_income: 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_dividend_income 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_dividend_income 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_dividend_income. 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_dividend_income 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 →