AI agents call batch_delete_gmail_emails to permanently remove resources in VaultAssist — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes email messages without possibility of recovery (beyond Gmail's trash bin with limited retention). Batch deletion increases blast radius—a misused agent could delete many emails simultaneously. While not financial, this is irreversible data loss and qualifies as Destructive, which ranks above Execute and Write in severity hierarchy.
From the tool's definition Tool name 'batch_delete_gmail_emails' and description 'Delete multiple emails at once' explicitly indicate irreversible deletion of email data. The batch operation amplifies the scope of destruction.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_delete_gmail_emails gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VaultAssist, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_delete_gmail_emails:
{
"version": "1",
"default": "deny",
"hide": [
"batch_delete_gmail_emails"
]
}batch_delete_gmail_emails disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete multiple emails at once. It is categorised as a Destructive tool in the VaultAssist MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the VaultAssist MCP server in PolicyLayer and add a rule for batch_delete_gmail_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 VaultAssist. Nothing to install.
batch_delete_gmail_emails 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 batch_delete_gmail_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.
Set action: deny in the PolicyLayer policy for batch_delete_gmail_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.
batch_delete_gmail_emails is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VaultAssist, 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.
79 VaultAssist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.