Deletes a Gmail filter
AI agents call delete_filter to permanently remove resources in Gmail AutoAuth MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a Gmail filter without the ability to undo the action directly through the API. Filters are important user-created rules that automatically organize, archive, or process incoming mail. Deleting a filter is an irreversible action that affects email management workflows. While not as critical as deleting actual emails, it constitutes destructive modification of user configuration.
From the tool's definition Tool name 'delete_filter' and description 'Deletes a Gmail filter' indicate irreversible deletion of user configuration data.
Attacks that exploit this kind of access
Deletes a Gmail filter. It is categorised as a Destructive tool in the Gmail AutoAuth MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gmail AutoAuth 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 Gmail AutoAuth MCP Server. Nothing to install.
delete_filter 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 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.
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.
delete_filter is provided by the Gmail AutoAuth MCP Server MCP server (sepehrshapouri/gmail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →