AI agents call get_dividend_data to retrieve information from Ashare without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves dividend and rights-issue information from a financial database. It has no side effects—it does not create, modify, delete, or execute operations. The data retrieved is read-only historical financial information. Severity is low because misuse would only expose or retrieve existing public financial data without causing damage, deletion, or financial transactions.
From the tool's definition Tool name 'get_dividend_data' and description 'Dividend / rights-issue records' indicate a data retrieval operation. The verb 'get' and the passive nature of retrieving historical dividend records show no modification or execution of external operations.
Attacks that exploit this kind of access
Dividend / rights-issue records. It is categorised as a Read tool in the Ashare MCP Server, which means it retrieves data without modifying state.
Register the Ashare MCP server in PolicyLayer and add a rule for get_dividend_data: 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 Ashare. Nothing to install.
get_dividend_data 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_data 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_data. 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_data is provided by the Ashare MCP server (maimai-hqw/ashare-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 →