Low Risk

get_trade_dates

get_trade_dates

How to control get_trade_dates ↓

What get_trade_dates does on A Share

AI agents call get_trade_dates 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_trade_dates needs a policy

This tool retrieves trading dates from a financial data server—a read-only query operation with no side effects. It returns data without modification, creation, deletion, or execution of external operations. The low severity reflects minimal harm potential even if misused by an AI agent; trade date information is public market data with no destructive, financial transaction, or code execution capabilities.

From the tool's definition Tool name 'get_trade_dates' and server description indicating 'data query' functionality. The server provides 'real-time quotes, historical K-line data, financial statements, technical indicators' and 'batch query' capabilities.

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

How to control get_trade_dates

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

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

get_trade_dates 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_trade_dates

What does the get_trade_dates tool do? +

get_trade_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_trade_dates? +

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

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

Can I rate-limit get_trade_dates? +

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

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

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