get_consecutive_limit_up
AI agents call get_consecutive_limit_up 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 historical or real-time data about stocks that have hit consecutive trading limit-ups (涨停). It performs no modifications, deletions, or external operations—merely queries and returns financial market data. The empty description reduces confidence slightly, but the naming convention and sibling tools strongly indicate a passive read operation with no side effects.
From the tool's definition Tool name 'get_consecutive_limit_up' suggests retrieval of data about consecutive daily price limit-up events.
Documented attack patterns abuse exactly the kind of access get_consecutive_limit_up 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_consecutive_limit_up:
{
"version": "1",
"default": "deny",
"tools": {
"get_consecutive_limit_up": {}
}
}get_consecutive_limit_up 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_consecutive_limit_up. 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_consecutive_limit_up: 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_consecutive_limit_up 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_consecutive_limit_up 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_consecutive_limit_up. 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_consecutive_limit_up 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.