Medium Risk

rename-mailbox

rename-mailbox

How to control rename-mailbox ↓

AI agents use rename-mailbox 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

Renaming a mailbox modifies email account structure but is reversible—the operation can be undone by renaming again. This qualifies as Write rather than Destructive. Severity is medium because misuse could confuse users or disrupt email organization, but causes no data loss. Confidence is moderate (0.85) due to empty description, though the tool name and server context strongly indicate the intended function.

From the tool's definition Tool name 'rename-mailbox' indicates modification of mailbox metadata. Context from sibling tools shows this server manages email operations via AppleScript, with destructive capabilities (batch-delete-messages, delete-mailbox) and write operations…

Documented attack patterns abuse exactly the kind of access rename-mailbox 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 rename-mailbox:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename-mailbox": {
      "limits": [
        {
          "counter": "rename-mailbox_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

rename-mailbox 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 rename-mailbox tool do? +

rename-mailbox. 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 rename-mailbox? +

Register the Apple Mail MCP server in PolicyLayer and add a rule for rename-mailbox: 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 rename-mailbox? +

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

Can I rate-limit rename-mailbox? +

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

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

rename-mailbox 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.