gmail_label_delete

Delete a user label entirely. The label disappears from every message that had it (the messages themselves are untouched). System labels (INBOX, SENT, etc.) cannot be deleted.

Server Mcp Gmail knowledgeislands/mcp-gmail
Category Destructive
Risk class Critical
Parameters 00 required

What gmail_label_delete does on Mcp Gmail

AI agents call gmail_label_delete to permanently remove resources in Mcp Gmail — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why gmail_label_delete needs a policy

This tool irreversibly deletes data (user-created labels) from the Gmail system. While the underlying messages are not deleted, the label metadata is permanently removed and cannot be recovered. This is an irreversible destructive action affecting potentially many messages at once.

From the tool's definition Tool description states 'Delete a user label entirely. The label disappears from every message that had it' — uses explicit 'Delete' verb and describes irreversible removal of a label from the system and all associated messages.

Risk signalsBulk/mass operation — affects multiple targets

Questions about gmail_label_delete

What does the gmail_label_delete tool do? +

Delete a user label entirely. The label disappears from every message that had it (the messages themselves are untouched). System labels (INBOX, SENT, etc.) cannot be deleted. It is categorised as a Destructive tool in the Mcp Gmail 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_label_delete? +

Register the Mcp Gmail MCP server in PolicyLayer and add a rule for gmail_label_delete: 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 Gmail. Nothing to install.

What risk level is gmail_label_delete? +

gmail_label_delete 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_label_delete? +

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

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

gmail_label_delete is provided by the Mcp Gmail MCP server (knowledgeislands/mcp-gmail). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.