delete_filter

THE RISK

Critical Risk

Why delete_filter needs a policy

This tool removes filter rules from Teradata WLM configuration without possibility of recovery. While the blast radius is limited to WLM filter configurations (not full database destruction), the permanent nature of the deletion and its impact on workload management rules that may be active in production justifies Destructive classification.

From the tool's definition Tool name is 'delete_filter' and description states 'PERMANENTLY DELETE a filter rule' — the use of 'PERMANENTLY' and 'DELETE' indicates irreversible removal of configuration data.

Documented attack patterns abuse exactly the kind of access delete_filter gives an agent:

POLICY

How to control delete_filter

PolicyLayer is an MCP gateway — it sits between your AI agents and Teradata Workload Management (WLM) MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_filter:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_filter"
  ]
}

delete_filter disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Teradata Workload Management (WLM) MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Teradata Workload Management (WLM) MCP Server tools

Destructive abort_delayed_request CANCEL and permanently abort a delayed query in the queue. The query will not execute and Destructive delete_throttle PERMANENTLY DELETE a throttle rule from the ruleset configuration. REQUIRES: ruleset_name, Destructive abort_sessions_user TERMINATES all active sessions for a specified user. This immediately kills all running qu Execute release_delay_queue Release a delayed query from the queue, allowing it to execute immediately. Use this to ma Execute activate_ruleset ACTIVATE a ruleset to apply ALL pending configuration changes to the live system. MUST BE Write add_classification_to_rule Add classification criteria to an existing rule (throttle, filter, or workload). Classific Write add_subcriteria_to_target Add sub-criteria to a target classification for advanced rule targeting. Sub-criteria type Write create_filter Create a filter rule to BLOCK or REJECT queries matching specific criteria. REQUIRES: rule

All 41 Teradata Workload Management (WLM) MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Teradata Workload Management (WLM) MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_filter

What does the delete_filter tool do? +

PERMANENTLY DELETE a filter rule. REQUIRES: ruleset_name, filter_name. CHANGES REQUIRE ACTIVATION. It is categorised as a Destructive tool in the Teradata Workload Management (WLM) MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_filter? +

Register the Teradata Workload Management (WLM) MCP Server MCP server in PolicyLayer and add a rule for delete_filter: 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 Teradata Workload Management (WLM) MCP Server. Nothing to install.

What risk level is delete_filter? +

delete_filter is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_filter? +

Yes. Add a rate_limit block to the delete_filter 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.

How do I block delete_filter completely? +

Set action: deny in the PolicyLayer policy for delete_filter. 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.

What MCP server provides delete_filter? +

delete_filter is provided by the Teradata Workload Management (WLM) MCP Server MCP server (teradata-labs/mcp-server-teradata-wlm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Teradata Workload Management (WLM) MCP Server tool call.

Start from Teradata Workload Management (WLM) MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →