Critical Risk →

mail.update_labels

Add or remove labels on a message

Part of the Hivekey server.

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

SECURE HIVEKEY →

Free to start. No card required.

AI agents may call mail.update_labels to permanently remove or destroy resources in Hivekey. 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 mail.update_labels in a loop, permanently destroying resources in Hivekey. 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": [
    "mail.update_labels"
  ]
}

See the full Hivekey policy for all 23 tools.

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

ENFORCE ON MY HIVEKEY →

View all 23 tools →

These attack patterns abuse exactly the kind of access mail.update_labels 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 mail.update_labels only ever does what you allow.

SECURE HIVEKEY →

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

What does the mail.update_labels tool do? +

Add or remove labels on a message. It is categorised as a Destructive tool in the Hivekey 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 mail.update_labels? +

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

What risk level is mail.update_labels? +

mail.update_labels 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 mail.update_labels? +

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

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

mail.update_labels is provided by the Hivekey MCP server (mailgent/hivekey). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Hivekey tool call.

Deterministic rules across all 23 Hivekey 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.