Critical Risk →

gmail_delete_draft

Deletes a Gmail draft message by its ID. This action cannot be undone.

How to control gmail_delete_draft ↓

What gmail_delete_draft does on MCP Google Workspace Server

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

Critical Risk

Why gmail_delete_draft needs a policy

This tool permanently removes a draft email message with no recovery mechanism. Deletion operations that cannot be undone fall under the Destructive category, which ranks higher in severity than Write (which implies reversible modifications).

From the tool's definition The description explicitly states 'Deletes a Gmail draft message' and 'This action cannot be undone.' The tool performs irreversible deletion of data.

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

How to control gmail_delete_draft

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

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

gmail_delete_draft 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 MCP Google Workspace 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 gmail_delete_draft

What does the gmail_delete_draft tool do? +

Deletes a Gmail draft message by its ID. This action cannot be undone. It is categorised as a Destructive tool in the MCP Google Workspace 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 gmail_delete_draft? +

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

What risk level is gmail_delete_draft? +

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

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

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

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

Enforce policy on every MCP Google Workspace Server tool call.

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

16 MCP Google Workspace 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.