连接管理：关闭当前 tqcenter 会话/连接；之后查询类工具需先重新 initialize。
AI agents call connection_close as a supporting operation in TdxQuant MCP Server workflows.
This tool closes a session/connection to the tqcenter service. It does not read, write, execute code, delete data, or move money. It terminates a network session, which is reversible (a new connection can be initialized). The closest category is Other, as session management is a lifecycle operation rather than a data or execution operation.
From the tool's definition 关闭当前 tqcenter 会话/连接；之后查询类工具需先重新 initialize
Documented attack patterns abuse exactly the kind of access connection_close 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 connection_close:
{
"version": "1",
"default": "deny",
"tools": {
"connection_close": {
"limits": [
{
"counter": "connection_close_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}connection_close gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
连接管理：关闭当前 tqcenter 会话/连接；之后查询类工具需先重新 initialize。. It is categorised as a Other tool in the TdxQuant MCP Server MCP Server, which means it performs auxiliary operations.
Register the TdxQuant MCP Server MCP server in PolicyLayer and add a rule for connection_close: 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.
connection_close is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the connection_close 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 connection_close. 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.
connection_close 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.