Get dividend history for a stock.
AI agents call get_dividends to retrieve information from yfinance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns dividend history data. It does not modify, delete, or execute any operations—it only retrieves read-only historical information. There is no financial transaction, code execution, or destructive action involved. The low severity reflects minimal blast radius; misuse would only expose or retrieve data already public via Yahoo Finance.
From the tool's definition Tool name 'get_dividends' and description 'Get dividend history for a stock' indicate a retrieval operation with no side effects. Returns historical financial data from Yahoo Finance.
Attacks that exploit this kind of access
Get dividend history for a stock. It is categorised as a Read tool in the yfinance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the yfinance 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 yfinance 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 yfinance MCP Server MCP server (torosent/yfinance-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 →