move_message · Mcp Imap MCP: Risk & Policy

WHAT IT DOES

What move_message does on Mcp Imap

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

WHY IT NEEDS A POLICY

Why move_message needs a policy

Moving a message between folders is a write operation that modifies email metadata (folder assignment) but does not delete or create new message content. It is reversible and does not execute arbitrary code or trigger external operations. While the server handles email management, this specific tool's function is to reorganize existing messages rather than read them, execute operations, or cause financial impact.

From the tool's definition Tool name 'move_message' with description 'Move a message to another folder' indicates modifying the organizational state of email data by relocating it between folders. This is a reversible operation—the message can be moved back.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_message Rate-limited

move_message 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_message": {
      "limits": [
        {
          "counter": "move_message_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 Mcp Imap, so you can run agents against it safely.

FAQ

Questions about move_message

What does the move_message tool do? +

Move a message to another folder. It is categorised as a Write tool in the Mcp Imap 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_message? +

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

What risk level is move_message? +

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

Can I rate-limit move_message? +

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

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

move_message is provided by the Mcp Imap MCP server (ngcdan/mcp-imap-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.