add_tag_to_emails · Zimbra MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_tag_to_emails does on Zimbra MCP Server

AI agents use add_tag_to_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 add_tag_to_emails needs a policy

Adding tags to emails is a metadata modification that creates or updates email properties without destructive or irreversible consequences. Tags can be removed, making this a Write-category action. The severity is low because misuse would only result in organizational changes to email metadata with no data loss, financial impact, or execution of external operations.

From the tool's definition Tool name 'add_tag_to_emails' and description 'Add a tag to emails' indicate the tool modifies email metadata by adding tags, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_tag_to_emails Rate-limited

add_tag_to_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": {
    "add_tag_to_emails": {
      "limits": [
        {
          "counter": "add_tag_to_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 add_tag_to_emails

What does the add_tag_to_emails tool do? +

Add a tag to 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 add_tag_to_emails? +

Register the Zimbra MCP Server MCP server in PolicyLayer and add a rule for add_tag_to_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 add_tag_to_emails? +

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

Can I rate-limit add_tag_to_emails? +

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

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

add_tag_to_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.