Critical Risk →

delete-filter

Deletes a specific filter

How to control delete-filter ↓

What delete-filter does on Enhanced Gmail MCP Server

AI agents call delete-filter to permanently remove resources in Enhanced Gmail MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete-filter needs a policy

Deleting a filter is an irreversible action that removes user-configured email rules permanently. While not as critical as deleting emails themselves, it destroys configuration data that cannot be easily recovered and can disrupt the user's email organization workflow.

From the tool's definition Tool name: 'delete-filter' with description 'Deletes a specific filter'. The verb 'deletes' indicates irreversible removal of a configured Gmail filter.

Documented attack patterns abuse exactly the kind of access delete-filter gives an agent:

How to control delete-filter

PolicyLayer is an MCP gateway — it sits between your AI agents and Enhanced Gmail 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.

  1. Create a free account and register Enhanced Gmail MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete-filter

What does the delete-filter tool do? +

Deletes a specific filter. It is categorised as a Destructive tool in the Enhanced Gmail 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 Enhanced Gmail 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 Enhanced Gmail 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 Enhanced Gmail MCP Server MCP server (theposch/gmail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Enhanced Gmail MCP Server tool call.

Start from Enhanced Gmail 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.

27 Enhanced Gmail MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.