AI agents call get_money_supply_data_year to retrieve information from A Share without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves macroeconomic indicator data (money supply by year) for analysis purposes. The 'get_' verb, server context focused on querying stock and financial data, and sibling tools all retrieving reference/historical data indicate this is a read-only query with no side effects, modifications, or external actions. Low severity since exposing financial reference data poses minimal direct risk.
From the tool's definition Tool name 'get_money_supply_data_year' and sibling tools like 'get_balance_data', 'get_cash_flow_data', 'get_deposit_rate_data' all use the 'get_' prefix indicating data retrieval. Server purpose is to 'query' financial and macroeconomic data.
Attacks that exploit this kind of access
get_money_supply_data_year. It is categorised as a Read tool in the A Share MCP Server, which means it retrieves data without modifying state.
Register the A Share 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 A Share. 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 A Share MCP server (kissjerryfan/mcp_server). 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 →