gmail_delete_label
AI agents call gmail_delete_label 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.
Deleting a label in Gmail permanently removes organizational metadata and may cause loss of message categorization. While not data destruction per se, label deletion is irreversible and affects email organization. This qualifies as Destructive rather than Write because the operation cannot be undone and has lasting consequences.
From the tool's definition Tool name 'gmail_delete_label' contains 'delete', which is an irreversible operation. The description is empty, but the name clearly indicates deletion of a Gmail label.
Attacks that exploit this kind of access
gmail_delete_label. 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.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for gmail_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 Mcp Gmail. Nothing to install.
gmail_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 gmail_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 gmail_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.
gmail_delete_label is provided by the Mcp Gmail MCP server (@monsoft/mcp-gmail). 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 →