AI agents use trade_order_stock to commit financial operations through TdxQuant MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
The tool name 'trade_order_stock' combined with the server's explicit mention of 'trading operations' and 'financial data and trading capabilities' strongly suggests this tool places stock orders, which constitutes a financial operation that could commit real monetary obligations. Despite the empty description, the naming convention and server context make financial classification highly likely.
From the tool's definition Tool name 'trade_order_stock' strongly implies placing stock trading orders; server description explicitly mentions 'trading operations'
Documented attack patterns abuse exactly the kind of access trade_order_stock 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_order_stock:
{
"version": "1",
"default": "deny",
"tools": {
"trade_order_stock": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to trade_order_stock is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
trade_order_stock. It is categorised as a Financial tool in the TdxQuant MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the TdxQuant MCP Server MCP server in PolicyLayer and add a rule for trade_order_stock: 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_order_stock is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the trade_order_stock 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_order_stock. 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_order_stock 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.