AI agents call trade_get_account_id 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 tool retrieves an account ID, which is data access with no side effects. Even though it relates to trading accounts (a financially-sensitive domain), the 'get' pattern and absence of modify/execute verbs indicate read-only retrieval. No evidence of execution, modification, deletion, or financial transaction capabilities.
From the tool's definition Tool name 'trade_get_account_id' indicates retrieval of account identifier. The naming convention 'get_*' and lack of mutation verbs suggests query-only behavior.
Documented attack patterns abuse exactly the kind of access trade_get_account_id 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_get_account_id:
{
"version": "1",
"default": "deny",
"tools": {
"trade_get_account_id": {}
}
}trade_get_account_id 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.
trade_get_account_id. 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_get_account_id: 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_get_account_id 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_get_account_id 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_get_account_id. 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_get_account_id 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.