imap_move_emails · Email MCP Server MCP: Risk & Policy

WHAT IT DOES

What imap_move_emails does on Email MCP Server

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

WHY IT NEEDS A POLICY

Why imap_move_emails needs a policy

Moving emails changes their folder location but does not delete or destroy data—the action is reversible (emails can be moved back). This qualifies as Write rather than Destructive. Severity is medium because misuse could reorganize or hide important emails, but the impact is limited to email organization without permanent data loss or financial consequences.

From the tool's definition Tool name 'imap_move_emails' indicates it modifies email state by relocating messages between mailboxes/folders.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

imap_move_emails Rate-limited

imap_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": {
    "imap_move_emails": {
      "limits": [
        {
          "counter": "imap_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 Email MCP Server, so you can run agents against it safely.

FAQ

Questions about imap_move_emails

What does the imap_move_emails tool do? +

imap_move_emails. It is categorised as a Write tool in the Email 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 imap_move_emails? +

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

What risk level is imap_move_emails? +

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

Can I rate-limit imap_move_emails? +

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

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

imap_move_emails is provided by the Email MCP Server MCP server (sventern/mcp_email). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.