Low Risk

get_last_n_trading_days

Return the last N trading dates.

How to control get_last_n_trading_days ↓

What get_last_n_trading_days does on A Share

AI agents call get_last_n_trading_days 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_last_n_trading_days needs a policy

This tool retrieves historical trading dates from the A-share market data service. It performs a straightforward read operation with no capability to modify data, execute code, delete records, or commit financial transactions. The severity is low because misuse (e.g., requesting trading dates) cannot cause harm or significant impact to systems or data.

From the tool's definition Tool name 'get_last_n_trading_days' and description 'Return the last N trading dates' indicate a retrieval operation that queries historical trading date information without modifying, executing external operations, or causing side effects.

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

How to control get_last_n_trading_days

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

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

get_last_n_trading_days 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_last_n_trading_days

What does the get_last_n_trading_days tool do? +

Return the last N trading dates. 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_last_n_trading_days? +

Register the A Share MCP server in PolicyLayer and add a rule for get_last_n_trading_days: 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_last_n_trading_days? +

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

Can I rate-limit get_last_n_trading_days? +

Yes. Add a rate_limit block to the get_last_n_trading_days 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_last_n_trading_days completely? +

Set action: deny in the PolicyLayer policy for get_last_n_trading_days. 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_last_n_trading_days? +

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