get_limit_down_pool
AI agents call get_limit_down_pool 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.
The tool is part of an A-share financial data query server dedicated to retrieving market data, historical K-lines, financial statements, and technical indicators. The 'get_' prefix and consistency with sibling Read-category tools (all get_* operations returning financial/market data) indicates this tool retrieves limit-down pool data without modifying it. No side effects are expected.
From the tool's definition Tool name contains 'get_limit_down_pool' (get operation); server description emphasizes 'data query' and matches sibling tools pattern (get_adjust_factor_data, get_balance_data, get_cash_flow_data, etc.) which are all data retrieval operations.
Documented attack patterns abuse exactly the kind of access get_limit_down_pool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and A Share, and nothing reaches the server without passing your rules. This is the rule we recommend for get_limit_down_pool:
{
"version": "1",
"default": "deny",
"tools": {
"get_limit_down_pool": {}
}
}get_limit_down_pool is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_limit_down_pool. 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_limit_down_pool: 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_limit_down_pool 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_limit_down_pool 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_limit_down_pool. 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_limit_down_pool is provided by the A Share MCP server (shouldnotappearcalm/a-share-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from A Share, 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.
55 A Share tools catalogued and risk-classified — across an index of 43,000+ MCP servers.