AI agents call calendar_get_trading_calendar to retrieve information from TdxQuant MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to query trading calendar information, which is reference/lookup data commonly needed for market operations. The 'get_' prefix indicates retrieval-only functionality with no modification, creation, or deletion of data. While the empty description reduces confidence slightly, the naming pattern and sibling tools on the server (all read-oriented queries) support classification as Read.
From the tool's definition Tool name 'calendar_get_trading_calendar' indicates a retrieval operation (get prefix) querying trading calendar data.
Documented attack patterns abuse exactly the kind of access calendar_get_trading_calendar gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TdxQuant MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for calendar_get_trading_calendar:
{
"version": "1",
"default": "deny",
"tools": {
"calendar_get_trading_calendar": {}
}
}calendar_get_trading_calendar 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.
calendar_get_trading_calendar. It is categorised as a Read tool in the TdxQuant MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TdxQuant MCP Server MCP server in PolicyLayer and add a rule for calendar_get_trading_calendar: 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 TdxQuant MCP Server. Nothing to install.
calendar_get_trading_calendar 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 calendar_get_trading_calendar 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 calendar_get_trading_calendar. 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.
calendar_get_trading_calendar is provided by the TdxQuant MCP Server MCP server (lingfan/tdxquant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TdxQuant MCP Server, 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.
39 TdxQuant MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.