GOOGLESUPER_DELETE_DRAFT
Permanently deletes a specific Gmail draft using its ID; ensure the draft exists and the user has necessary permissions for the given user_id.
This record as markdown: /tools/googlesuper/googlesuper-delete-draft.md
What GOOGLESUPER_DELETE_DRAFT does on Google Super
AI agents call GOOGLESUPER_DELETE_DRAFT to permanently remove resources in Google Super, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
user_id | string | — | User's email address or 'me' for the authenticated user; 'me' is recommended. |
draft_id | string | — | Immutable ID of the draft to delete, typically obtained when the draft was created. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_DELETE_DRAFT is rated Critical
This tool destroys data that cannot be recovered. Permanent deletion of Gmail drafts is an irreversible action. While the blast radius is somewhat limited to a single draft (not organization-wide), the destructive nature and the fact that users may have unsaved work in drafts elevates this to 'high' severity. An AI agent misusing this could permanently erase users' draft messages without recovery options.
From the tool's definition 'Permanently deletes a specific Gmail draft' — the verb 'deletes' combined with the adverb 'permanently' clearly indicates irreversible data destruction.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_DELETE_DRAFT safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_DELETE_DRAFT, this is the rule to start with:
GOOGLESUPER_DELETE_DRAFT is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_DELETE_DRAFT call is checked against it from then on.
Questions about GOOGLESUPER_DELETE_DRAFT
Permanently deletes a specific Gmail draft using its ID; ensure the draft exists and the user has necessary permissions for the given user_id. It is categorised as a Destructive tool in the Google Super MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
GOOGLESUPER_DELETE_DRAFT accepts 2 parameters: user_id, draft_id. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_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 Google Super. Nothing to install.
GOOGLESUPER_DELETE_DRAFT 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 GOOGLESUPER_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.
Set action: deny in the PolicyLayer policy for GOOGLESUPER_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.
GOOGLESUPER_DELETE_DRAFT is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
Across the catalogue