imap_rename_folder · Email MCP Server MCP: Risk & Policy

WHAT IT DOES

What imap_rename_folder does on Email MCP Server

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

WHY IT NEEDS A POLICY

Why imap_rename_folder needs a policy

Renaming a folder is a reversible write operation that modifies the state of email organization. It does not delete data (ruling out Destructive), execute code (ruling out Execute), or move money (ruling out Financial). The severity is medium rather than high because the impact is localized to folder metadata; misuse would reorganize emails but not destroy them or expose sensitive operations.

From the tool's definition The tool name 'imap_rename_folder' and description 'Rename a folder/mailbox' directly indicate a modification operation that changes metadata of an email folder without deleting or destroying it.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

imap_rename_folder Rate-limited

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

FAQ

Questions about imap_rename_folder

What does the imap_rename_folder tool do? +

Rename a folder/mailbox. It is categorised as a Write tool in the Email 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 imap_rename_folder? +

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

What risk level is imap_rename_folder? +

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

Can I rate-limit imap_rename_folder? +

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

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

imap_rename_folder is provided by the Email MCP Server MCP server (sventern/mcp_email). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.