Get historical dividend payout data for a given stock.
AI agents call get_dividends to retrieve information from Yahoo Finance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical financial information about dividend payouts for a stock. It is a read-only query that does not create, modify, delete, or execute any operations. While the server deals with financial data, this specific tool only retrieves publicly available information and makes no financial transactions or commitments.
From the tool's definition Tool name is 'get_dividends' and description states it retrieves 'historical dividend payout data' — a read-only query operation with no side effects.
Attacks that exploit this kind of access
Get historical dividend payout data for a given stock. It is categorised as a Read tool in the Yahoo Finance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Yahoo Finance MCP Server MCP server in PolicyLayer and add a rule for get_dividends: 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 Yahoo Finance MCP Server. Nothing to install.
get_dividends 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 get_dividends 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 get_dividends. 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.
get_dividends is provided by the Yahoo Finance MCP Server MCP server (peidaqi/yfinance-mcp-server). 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 →