proton_move_email · Proton MCP Server MCP: Risk & Policy

WHAT IT DOES

What proton_move_email does on Proton MCP Server

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

WHY IT NEEDS A POLICY

Why proton_move_email needs a policy

Moving an email between folders is a write operation because it modifies the state of an email (its folder location) reversibly. It is not Destructive because the email remains intact and recoverable from the destination folder. It is not Destructive because moving is not an irreversible deletion.

From the tool's definition Tool performs 'Move an email from one folder to another' - a reversible modification operation that changes email metadata/location without deleting or destroying data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

proton_move_email Rate-limited

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

FAQ

Questions about proton_move_email

What does the proton_move_email tool do? +

Move an email from one folder to another. Specify source folder, email UID, and destination folder. It is categorised as a Write tool in the Proton 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 proton_move_email? +

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

What risk level is proton_move_email? +

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

Can I rate-limit proton_move_email? +

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

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

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