Return a date range string covering the recent N trading days.
AI agents call get_recent_trading_range 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 and returns a date range for recent trading days. It performs a data query operation with no side effects, modification of data, code execution, or financial impact. It is purely informational and matches the 'Read' category pattern of retrieving/querying data. The context of an A-share market data server further confirms this is a simple query utility with minimal risk.
From the tool's definition Tool description states 'Return a date range string covering the recent N trading days' - returns data with no modification or side effects
Documented attack patterns abuse exactly the kind of access get_recent_trading_range 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_recent_trading_range:
{
"version": "1",
"default": "deny",
"tools": {
"get_recent_trading_range": {}
}
}get_recent_trading_range 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.
Return a date range string covering the recent N trading days. 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_recent_trading_range: 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_recent_trading_range 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_recent_trading_range 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_recent_trading_range. 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_recent_trading_range 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.