AI agents call financial_get_report_range 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.
The 'get' prefix and sibling tools like 'financial_get_report_by_date' indicate this retrieves financial data without modification. No evidence of write, execute, destructive, or financial transaction capabilities. The empty description lowers confidence slightly, but the consistent naming pattern with other read-only tools on the server supports this classification.
From the tool's definition Tool name 'financial_get_report_range' contains 'get' and 'report', indicating data retrieval. No description provided, but naming convention suggests querying financial reports within a date/range range.
Documented attack patterns abuse exactly the kind of access financial_get_report_range 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 financial_get_report_range:
{
"version": "1",
"default": "deny",
"tools": {
"financial_get_report_range": {}
}
}financial_get_report_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.
financial_get_report_range. 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 financial_get_report_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 TdxQuant MCP Server. Nothing to install.
financial_get_report_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 financial_get_report_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 financial_get_report_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.
financial_get_report_range 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.