Low Risk

get_limit_up_down

get_limit_up_down

How to control get_limit_up_down ↓

What get_limit_up_down does on A Share

AI agents call get_limit_up_down 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.

Low Risk

Why get_limit_up_down needs a policy

This is a read-only data query tool for A-share market information. 'Limit up' and 'limit down' are price movement statistics in Chinese stock markets. The tool retrieves historical or real-time data about these movements with no capability to modify, execute, or delete data.

From the tool's definition Tool name 'get_limit_up_down' indicates data retrieval. Server description emphasizes 'data query' capabilities ('全方位数据查询'), and sibling tools (get_adjust_factor_data, get_all_stock, get_balance_data, get_dividend_data, etc.) are all read-only queries of…

Documented attack patterns abuse exactly the kind of access get_limit_up_down gives an agent:

How to control get_limit_up_down

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_up_down:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_limit_up_down": {}
  }
}

get_limit_up_down is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register A Share — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_limit_up_down

What does the get_limit_up_down tool do? +

get_limit_up_down. It is categorised as a Read tool in the A Share MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_limit_up_down? +

Register the A Share MCP server in PolicyLayer and add a rule for get_limit_up_down: 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.

What risk level is get_limit_up_down? +

get_limit_up_down is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_limit_up_down? +

Yes. Add a rate_limit block to the get_limit_up_down 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.

How do I block get_limit_up_down completely? +

Set action: deny in the PolicyLayer policy for get_limit_up_down. 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.

What MCP server provides get_limit_up_down? +

get_limit_up_down 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.

Enforce policy on every A Share tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.