Critical Risk →

GMAIL_REMOVE_LABEL

Permanently deletes a specific, existing user-created gmail label by its id for a user; cannot delete system labels.

Part of the Gmail server.

GMAIL_REMOVE_LABEL can permanently delete data in Gmail, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE GMAIL →

Free to start. No card required.

AI agents may call GMAIL_REMOVE_LABEL to permanently remove or destroy resources in Gmail. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call GMAIL_REMOVE_LABEL in a loop, permanently destroying resources in Gmail. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

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

See the full Gmail policy for all 20 tools.

Get this rule live on your own Gmail server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY GMAIL →

View all 20 tools →

These attack patterns abuse exactly the kind of access GMAIL_REMOVE_LABEL gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so GMAIL_REMOVE_LABEL only ever does what you allow.

SECURE GMAIL →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the GMAIL_REMOVE_LABEL tool do? +

Permanently deletes a specific, existing user-created gmail label by its id for a user; cannot delete system labels.. 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.

How do I enforce a policy on GMAIL_REMOVE_LABEL? +

Register the Gmail MCP server in PolicyLayer and add a rule for GMAIL_REMOVE_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.

What risk level is GMAIL_REMOVE_LABEL? +

GMAIL_REMOVE_LABEL 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_REMOVE_LABEL? +

Yes. Add a rate_limit block to the GMAIL_REMOVE_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.

How do I block GMAIL_REMOVE_LABEL completely? +

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

What MCP server provides GMAIL_REMOVE_LABEL? +

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

Enforce policy on every Gmail tool call.

Deterministic rules across all 20 Gmail tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.