AI agents call trade_query_positions 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 retrieves current trading positions from a financial account, making it a Read operation. While it does not modify, delete, or execute transactions, the sensitivity of financial account data and the context of a trading system elevates severity to 'high' due to potential for unauthorized disclosure of investment holdings and portfolio composition.
From the tool's definition Tool name 'trade_query_positions' and description '交易接口：查询当前持仓' (Trading interface: query current positions) retrieves financial position data without modifying it. The word '查询' (query) confirms read-only behavior.
Documented attack patterns abuse exactly the kind of access trade_query_positions 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 trade_query_positions:
{
"version": "1",
"default": "deny",
"tools": {
"trade_query_positions": {}
}
}trade_query_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 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 trade_query_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 TdxQuant MCP Server. Nothing to install.
trade_query_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 trade_query_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 trade_query_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.
trade_query_positions 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.