Fetch historical dividend data with pagination
AI agents call fetch_paid_out_dividends to retrieve information from Trading 212 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 (dividend records) without modifying data, executing trades, or moving money. It is a straightforward read operation analogous to fetching account statements or transaction history. While it provides financial data, the tool itself does not commit financial obligations, execute trades, or delete data.
From the tool's definition Tool name and description indicate it 'Fetches historical dividend data' — a retrieval operation with no modification or execution capability. The pagination parameter confirms it is a query/list operation.
Attacks that exploit this kind of access
Fetch historical dividend data with pagination. It is categorised as a Read tool in the Trading 212 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Trading 212 MCP Server MCP server in PolicyLayer and add a rule for fetch_paid_out_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 Trading 212 MCP Server. Nothing to install.
fetch_paid_out_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 fetch_paid_out_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 fetch_paid_out_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.
fetch_paid_out_dividends is provided by the Trading 212 MCP Server MCP server (razeevascx/212mcp). 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 →