move_emails · Zimbra MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_emails does on Zimbra MCP Server

AI agents use move_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 move_emails needs a policy

Moving emails changes their state (folder assignment) reversibly. It is not a Read operation (does not merely retrieve data), not Execute (does not run code or trigger external operations with argument-dependent effects), not Destructive (reversible, not a permanent deletion), and not Financial. Write is the appropriate category.

From the tool's definition Tool description states 'Move emails to a folder' — this modifies the location/organization of existing emails.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_emails Rate-limited

move_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": {
    "move_emails": {
      "limits": [
        {
          "counter": "move_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 move_emails

What does the move_emails tool do? +

Move emails to a folder. 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 move_emails? +

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

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

Can I rate-limit move_emails? +

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

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

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