batch_delete_emails

Permanently deletes multiple emails in batches

Server Gmail AutoAuth MCP Server sepehrshapouri/gmail-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What batch_delete_emails does on Gmail AutoAuth MCP Server

AI agents call batch_delete_emails 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.

Why batch_delete_emails needs a policy

This tool irreversibly removes email data with no recovery mechanism. While severity is not critical (no financial impact or system-level damage), the permanent nature of bulk deletion and potential for accidental loss of important communications justifies 'high' severity. An AI agent with misaligned objectives could delete years of user emails.

From the tool's definition Tool name 'batch_delete_emails' and description 'Permanently deletes multiple emails in batches' indicate irreversible deletion of data. The word 'Permanently' explicitly confirms this cannot be undone.

Risk signalsBulk/mass operation — affects multiple targets

Questions about batch_delete_emails

What does the batch_delete_emails tool do? +

Permanently deletes multiple emails in batches. 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.

How do I enforce a policy on batch_delete_emails? +

Register the Gmail AutoAuth MCP Server MCP server in PolicyLayer and add a rule for batch_delete_emails: 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.

What risk level is batch_delete_emails? +

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

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

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

batch_delete_emails 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.

// THE FULL RECORD

batch_delete_emails is one line of Gmail AutoAuth MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.