// SCAN REPORT

Mail

25 tools. 14 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

14 can modify or destroy data

11 read-only

25 tools total

Community server · catalogue entry verified 30/06/2026

How to control Mail ↓

TOOL MAP

What Mail exposes to your agents

Read (11) Write / Execute (11) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Mail tools

Destructive · High delete_folder Deleting a folder is a destructive action that cannot be undone—it removes data permanently. Destructive · High delete_messages This tool irreversibly removes data (email messages) and cannot be undone. Destructive · Medium trash_messages While the description notes it is 'recoverable', moving messages to Trash is semantically a delete operation and maps to the Destructive category. Write · Medium archive_messages Archiving messages modifies email organization by moving them to a designated folder.

14 of Mail's 25 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Mail

PolicyLayer is an MCP gateway — it sits between your AI agents and Mail, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_folder": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "archive_messages": {
    "limits": [
      {
        "counter": "archive_messages_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_inbox": {
    "limits": [
      {
        "counter": "check_inbox_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Mail — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MAIL →

Instant setup, no code required.

FULL CATALOGUE

All 25 Mail tools

DESTRUCTIVE 3 tools

Destructive delete_folder Delete an IMAP folder. Destructive delete_messages Permanently delete messages from a folder. Destructive trash_messages Move messages to Trash (recoverable delete).

WRITE 11 tools

Write archive_messages Archive messages — moves them to the Archive folder. Write create_folder Create a new IMAP folder. Write forward_message forward_message Write mark_as_spam Report messages as spam and move them to the Spam/Junk folder. Write mark_messages Add or remove standard IMAP flags on messages. Write move_messages Move messages from one folder to another. Write rename_folder Rename an IMAP folder. Write reply_message reply_message Write save_draft save_draft Write send_message send_message Write set_labels set_labels

READ 11 tools

Read check_inbox Quick inbox check: unread count + last N message summaries. Read daily_digest Structured daily overview: unread, flagged, and today's messages. Read download_attachment download_attachment Read find_unread Shortcut: list unread messages in a folder. Equivalent to list_messages(unseen_only=True). Read get_message Fetch the full content of a message by UID. Read get_thread Retrieve all messages in a thread by Message-ID. Read list_folders List all IMAP folders on the account. Read list_labels List all user-defined keyword labels available on a folder (PERMANENTFLAGS). Read list_messages List messages in a folder. Read mail_guide Return a complete guide of available tools and best usage patterns for mail-mcp. Read search_messages search_messages

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Mail

Can an AI agent delete data through the Mail MCP server? +

Yes. The Mail server exposes 3 destructive tools including delete_folder, delete_messages, trash_messages. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Mail? +

The Mail server has 11 write tools including archive_messages, create_folder, forward_message. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Mail.

How many tools does the Mail MCP server expose? +

25 tools across 3 categories: Destructive, Read, Write. 11 are read-only. 14 can modify, create, or delete data.

How do I enforce a policy on Mail? +

Register the Mail MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Mail tool call.

Deterministic rules across all 25 Mail tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MAIL →

Instant setup, no code required.

25 Mail tools catalogued and risk-classified — across an index of 43,000+ MCP servers.