Medium Risk

batch-move-messages

batch-move-messages

How to control batch-move-messages ↓

AI agents use batch-move-messages to create or update resources in Apple Mail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Mail environment.

Medium Risk

Moving messages is a write operation that modifies email state (mailbox location) reversibly—messages can be moved back. It does not delete data irreversibly (which would be Destructive) nor execute arbitrary code (which would be Execute). However, the batch nature and potential to move large volumes of messages to incorrect mailboxes or spam folders creates a moderate blast radius.

From the tool's definition Tool name 'batch-move-messages' indicates bulk relocation of messages. Related tools on the same server include 'batch-delete-messages', 'batch-flag-messages', 'batch-mark-as-read', and 'delete-message', which establish the pattern of message manipulation…

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access batch-move-messages gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Mail, and nothing reaches the server without passing your rules. This is the rule we recommend for batch-move-messages:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "batch-move-messages": {
      "limits": [
        {
          "counter": "batch-move-messages_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

batch-move-messages 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.

  1. Create a free account and register Apple Mail — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the batch-move-messages tool do? +

batch-move-messages. It is categorised as a Write tool in the Apple Mail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on batch-move-messages? +

Register the Apple Mail MCP server in PolicyLayer and add a rule for batch-move-messages: 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 Apple Mail. Nothing to install.

What risk level is batch-move-messages? +

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

Can I rate-limit batch-move-messages? +

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

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

batch-move-messages is provided by the Apple Mail MCP server (sweetrb/apple-mail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Apple Mail tool call.

Deterministic rules across all 40 Apple Mail tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

40 Apple Mail tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.