Low Risk

get_dividend_yield

Fetches historical dividend yield data for a given ticker.

How to control get_dividend_yield ↓

What get_dividend_yield does on MCP Tiingo Server

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.

Low Risk

Why get_dividend_yield needs a policy

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:

How to control get_dividend_yield

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:

policy.json
{
  "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.

  1. Create a free account and register MCP Tiingo Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_dividend_yield

What does the get_dividend_yield tool do? +

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.

How do I enforce a policy on get_dividend_yield? +

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.

What risk level is get_dividend_yield? +

get_dividend_yield is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_dividend_yield? +

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.

How do I block get_dividend_yield completely? +

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.

What MCP server provides get_dividend_yield? +

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.

Enforce policy on every MCP Tiingo Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.