Delete a Gmail user label by its ID. System labels (INBOX, SENT, etc.) cannot be deleted.
AI agents call delete_label to permanently remove resources in Gmail — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a label is an irreversible action that removes organizational metadata and cannot be undone without manual recreation. While system labels have protection, user-created labels can be permanently removed, resulting in loss of email organization and categorization. This is more severe than Write (which is reversible) but less severe than Financial.
From the tool's definition Tool name is 'delete_label' and description states 'Delete a Gmail user label by its ID'. The verb 'delete' combined with irreversible removal of user-created labels indicates destructive capability.
Attacks that exploit this kind of access
Delete a Gmail user label by its ID. System labels (INBOX, SENT, etc.) cannot be deleted. It is categorised as a Destructive tool in the Gmail MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gmail MCP server in PolicyLayer and add a rule for delete_label: 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. Nothing to install.
delete_label 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 delete_label 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 delete_label. 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.
delete_label is provided by the Gmail MCP server (ndungukamami-sketch/gmail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →