delete_gmail_email

THE RISK

Critical Risk

Why delete_gmail_email needs a policy

Deleting email is irreversible and destroys data. Although scoped to a single email (lower blast radius than batch operations), it still meets the Destructive category definition. Severity is high because email often contains sensitive information, financial records, or compliance-relevant communications, and deletion cannot be undone.

From the tool's definition Tool name includes 'delete' and description states 'Delete an email by its message ID' — this permanently removes email data without reversal.

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

POLICY

How to control delete_gmail_email

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 delete_gmail_email:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_gmail_email"
  ]
}

delete_gmail_email disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register VaultAssist — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More VaultAssist tools

Destructive batch_delete_gmail_emails Delete multiple emails at once Destructive clear_completed_tasks Clear all completed tasks from a task list. The tasks will be marked as hidden Destructive delete_event Delete an event from a Google Calendar Destructive delete_gmail_label Delete a Gmail label Destructive delete_task Delete a task from a task list Destructive delete_task_list Delete a task list. Note: This will also delete all tasks in the list Destructive memory_delete_entities Delete and forget multiple entities and their associated relationships from the user Destructive memory_delete_observations Delete and forget specific observations, details, or information from entities in the user

All 79 VaultAssist tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in VaultAssist → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_gmail_email

What does the delete_gmail_email tool do? +

Delete an email by its message ID. 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.

How do I enforce a policy on delete_gmail_email? +

Register the VaultAssist MCP server in PolicyLayer and add a rule for delete_gmail_email: 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.

What risk level is delete_gmail_email? +

delete_gmail_email 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_gmail_email? +

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

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

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

Enforce policy on every VaultAssist tool call.

Start from VaultAssist, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →