Medium Risk

mail__move_message

Move an email to a different folder (e.g. Trash, Archive, a label)

How to control mail__move_message ↓

What mail__move_message does on Proton-MCP

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

Medium Risk

Why mail__move_message needs a policy

Moving a message between folders is a reversible modification of email metadata/organization. It does not delete data permanently (which would be Destructive), does not execute arbitrary code (Execute), and does not involve financial transactions (Financial). The action can be undone by moving the message back, classifying it as Write.

From the tool's definition Tool name 'mail__move_message' and description 'Move an email to a different folder (e.g. Trash, Archive, a label)' indicates the tool modifies the location/state of an existing email message.

Documented attack patterns abuse exactly the kind of access mail__move_message gives an agent:

How to control mail__move_message

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mail__move_message": {
      "limits": [
        {
          "counter": "mail__move_message_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Proton-MCP — 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.

Related tools and policies

Go deeper

Questions about mail__move_message

What does the mail__move_message tool do? +

Move an email to a different folder (e.g. Trash, Archive, a label). It is categorised as a Write tool in the Proton-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mail__move_message? +

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

What risk level is mail__move_message? +

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

Can I rate-limit mail__move_message? +

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

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

mail__move_message is provided by the Proton- MCP server (jorgenclaw/proton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Proton-MCP tool call.

Start from Proton-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

36 Proton-MCP tools catalogued and risk-classified — across an index of 43,000+ 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.