remove_tag_from_emails · Zimbra MCP Server MCP

WHAT IT DOES

What remove_tag_from_emails does on Zimbra MCP Server

AI agents use remove_tag_from_emails to create or update resources in Zimbra MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zimbra MCP Server environment.

WHY IT NEEDS A POLICY

Why remove_tag_from_emails needs a policy

Removing a tag from emails modifies the metadata/labeling of emails but does not delete the emails themselves. This is a reversible modification (the tag can be re-added), placing it in the Write category. Misuse could affect email organization at scale, warranting medium severity.

From the tool's definition Remove a tag from emails

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_tag_from_emails Rate-limited

remove_tag_from_emails stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "remove_tag_from_emails": {
      "limits": [
        {
          "counter": "remove_tag_from_emails_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Zimbra MCP Server, so you can run agents against it safely.

FAQ

Questions about remove_tag_from_emails

What does the remove_tag_from_emails tool do? +

Remove a tag from emails. It is categorised as a Write tool in the Zimbra MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on remove_tag_from_emails? +

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

What risk level is remove_tag_from_emails? +

remove_tag_from_emails is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit remove_tag_from_emails? +

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

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

remove_tag_from_emails is provided by the Zimbra MCP Server MCP server (jeremie-lesage/zimbra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.