Critical Risk →

deleteGmailFilter

Delete a Gmail filter.

How to control deleteGmailFilter ↓

What deleteGmailFilter does on Google Workspace MCP Server

AI agents call deleteGmailFilter to permanently remove resources in Google Workspace MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why deleteGmailFilter needs a policy

This tool permanently removes a Gmail filter without possibility of recovery through the tool itself. While not as severe as deleting emails directly, deletion of filters can disrupt email organization, potentially cause important emails to be misrouted, and cannot be undone by the tool.

From the tool's definition The tool name 'deleteGmailFilter' combined with the description 'Delete a Gmail filter' explicitly indicates irreversible deletion of a Gmail filter configuration. The verb 'delete' is a clear destructive action.

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

How to control deleteGmailFilter

PolicyLayer is an MCP gateway — it sits between your AI agents and Google Workspace MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deleteGmailFilter:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "deleteGmailFilter"
  ]
}

deleteGmailFilter 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 Google Workspace 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 deleteGmailFilter

What does the deleteGmailFilter tool do? +

Delete a Gmail filter. It is categorised as a Destructive tool in the Google Workspace 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 deleteGmailFilter? +

Register the Google Workspace MCP Server MCP server in PolicyLayer and add a rule for deleteGmailFilter: 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 Google Workspace MCP Server. Nothing to install.

What risk level is deleteGmailFilter? +

deleteGmailFilter 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 deleteGmailFilter? +

Yes. Add a rate_limit block to the deleteGmailFilter 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 deleteGmailFilter completely? +

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

deleteGmailFilter is provided by the Google Workspace MCP Server MCP server (sputnicyoji/google-workspace-mcp-with-script). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Workspace MCP Server tool call.

Start from Google Workspace 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.

72 Google Workspace 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.