AI agents call query_account_positions 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 queries and retrieves existing account position information. It has no side effects—it does not create, modify, delete, or execute any financial transactions. While it exists within a financial trading system (QMT), the tool itself only performs data retrieval, making it a Read category risk.
From the tool's definition Tool name 'query_account_positions' and description '查询账户持仓' (query account positions) clearly indicate a read-only operation that retrieves position data without modifying, deleting, or executing trades.
Documented attack patterns abuse exactly the kind of access query_account_positions 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 query_account_positions:
{
"version": "1",
"default": "deny",
"tools": {
"query_account_positions": {}
}
}query_account_positions 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.
查询账户持仓. 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 query_account_positions: 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.
query_account_positions 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 query_account_positions 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 query_account_positions. 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.
query_account_positions is provided by the QMT-MCP-Server MCP server (nnquant/qmt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 QMT-MCP-Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 QMT-MCP-Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.