Fetches historical dividend yield data for a given ticker.
AI agents call get_dividend_yield to retrieve information from MCP Tiingo 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 metrics (dividend yield) for analysis purposes. It performs a read-only query against the Tiingo API with no side effects, reversible modifications, code execution, destructive actions, or financial transactions. The severity is low because accessing historical market data poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_dividend_yield' and description 'Fetches historical dividend yield data' indicate data retrieval with no modification, deletion, or financial transaction capability.
Documented attack patterns abuse exactly the kind of access get_dividend_yield gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Tiingo Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dividend_yield:
{
"version": "1",
"default": "deny",
"tools": {
"get_dividend_yield": {}
}
} get_dividend_yield is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetches historical dividend yield data for a given ticker. It is categorised as a Read tool in the MCP Tiingo Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Tiingo Server MCP server in PolicyLayer and add a rule for get_dividend_yield: 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 MCP Tiingo Server. Nothing to install.
get_dividend_yield 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_dividend_yield 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_dividend_yield. 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_dividend_yield is provided by the MCP Tiingo Server MCP server (matteoantoci/mcp-tiingo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Tiingo Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 MCP Tiingo Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.