Delete a filter group permanently. Detaches it from any tools that
AI agents call qd_delete_filter_group to permanently remove resources in QuantData MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data and cannot be undone, making it Destructive rather than Write. While the blast radius is limited to filter groups (not financial accounts or trading operations), permanent deletion of user-created filters could impact market analysis workflows. Severity is high because accidental deletion could disrupt analysis capabilities, though the financial impact is indirect.
From the tool's definition qd_delete_filter_group performs permanent deletion of a filter group ("Delete a filter group permanently"). The word "Delete" combined with "permanently" indicates irreversible data removal.
Documented attack patterns abuse exactly the kind of access qd_delete_filter_group gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QuantData MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for qd_delete_filter_group:
{
"version": "1",
"default": "deny",
"hide": [
"qd_delete_filter_group"
]
} qd_delete_filter_group 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.
Delete a filter group permanently. Detaches it from any tools that. It is categorised as a Destructive tool in the QuantData MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the QuantData MCP Server MCP server in PolicyLayer and add a rule for qd_delete_filter_group: 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 QuantData MCP Server. Nothing to install.
qd_delete_filter_group 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 qd_delete_filter_group 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 qd_delete_filter_group. 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.
qd_delete_filter_group is provided by the QuantData MCP Server MCP server (zzulanas/quantdata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from QuantData 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.
50 QuantData MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.