move_email · ProtonMail MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_email does on ProtonMail MCP Server

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

WHY IT NEEDS A POLICY

Why move_email needs a policy

Moving an email to a different folder is a write operation that changes email organization state reversibly. It does not permanently delete data (which would be Destructive), nor does it involve financial transactions (Financial), nor does it execute arbitrary code (Execute).

From the tool's definition Tool name is 'move_email' with description 'Move an email to a different folder'. This operation modifies the state of email metadata (folder assignment) but is reversible—the email can be moved back or recovered.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_email Rate-limited

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

FAQ

Questions about move_email

What does the move_email tool do? +

Move an email to a different folder. It is categorised as a Write tool in the ProtonMail 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 move_email? +

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

What risk level is move_email? +

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

Can I rate-limit move_email? +

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

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

move_email is provided by the ProtonMail MCP Server MCP server (ronamosa/protonmail-pro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.