AI agents call get_money_supply_data_year 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 retrieves macroeconomic time-series data (money supply metrics) from a financial data provider. It is a read-only query operation with no side effects, no code execution, no data modification, and no financial transactions. The low severity reflects minimal blast radius—misuse would only expose public economic data already available through standard financial information sources.
From the tool's definition Tool name 'get_money_supply_data_year' and description 'Yearly money supply M0/M1/M2' indicate retrieval of historical monetary statistics with date parameter 'YYYY'. No modification, deletion, execution, or financial transaction capability.
Attacks that exploit this kind of access
Yearly money supply M0/M1/M2 (货币供应量-年). Dates 'YYYY'. 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_money_supply_data_year: 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_money_supply_data_year 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_money_supply_data_year 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_money_supply_data_year. 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_money_supply_data_year 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 →