AI agents call utility_delete_sector to permanently remove resources in TdxQuant MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes user-defined sector configurations without the ability to undo the operation. This is a Destructive action as it irreversibly deletes data. Severity is high because unintended deletion of custom sector definitions could disrupt trading strategies and analysis workflows, though the blast radius is limited to sector metadata rather than financial accounts or market positions.
From the tool's definition Tool name contains 'delete' and description explicitly states '删除自定义板块' (delete custom sectors). This is an irreversible data deletion operation.
Documented attack patterns abuse exactly the kind of access utility_delete_sector 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 utility_delete_sector:
{
"version": "1",
"default": "deny",
"hide": [
"utility_delete_sector"
]
}utility_delete_sector disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
工具/缓存：删除自定义板块。. It is categorised as a Destructive tool in the TdxQuant MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TdxQuant MCP Server MCP server in PolicyLayer and add a rule for utility_delete_sector: 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.
utility_delete_sector is a Destructive 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 utility_delete_sector 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 utility_delete_sector. 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.
utility_delete_sector 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.