AI agents call download_history_data2_tool to retrieve information from QMT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical market data from the QMT platform for A-share securities. Despite the empty description, the sibling tool and server context make it clear this is a read-only operation that queries and downloads existing market data. No modification, deletion, code execution, or financial transactions are involved.
From the tool's definition Tool name contains 'download_history_data' and is a sibling of 'download_history_data_tool'; server description states it enables users to 'download historical market data' for analysis.
Documented attack patterns abuse exactly the kind of access download_history_data2_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QMT MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for download_history_data2_tool:
{
"version": "1",
"default": "deny",
"tools": {
"download_history_data2_tool": {}
}
}download_history_data2_tool 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.
download_history_data2_tool. It is categorised as a Read tool in the QMT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QMT MCP Server MCP server in PolicyLayer and add a rule for download_history_data2_tool: 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 QMT MCP Server. Nothing to install.
download_history_data2_tool 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 download_history_data2_tool 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 download_history_data2_tool. 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.
download_history_data2_tool is provided by the QMT MCP Server MCP server (jm12138/qmt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from QMT 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.
5 QMT MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.