// SCAN REPORT

IMAP Email MCP Server

10 tools. 4 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 12 Jun 2026

4 can modify or destroy data

6 read-only

10 tools total

Community server · catalogue entry verified 12/06/2026

How to control IMAP Email MCP Server ↓

TOOL MAP

What IMAP Email MCP Server exposes to your agents

Read (6) Write / Execute (3) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous IMAP Email MCP Server tools

Destructive · High delete_email Email deletion permanently removes messages and cannot be undone. Write · Medium create_draft This tool creates new data (email draft) but does not send it or make it irreversible. Write · High send_email Sending emails is a reversible write operation—messages can be retrieved/deleted post-send, but the act commits content to external systems (recipients' inboxes) with potential consequences (spam, impersonation, leaked d Write · Medium update_draft This tool creates or modifies email drafts, which are not yet sent and can be further edited or deleted.

4 of IMAP Email MCP Server's 10 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control IMAP Email MCP Server

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

Deny destructive operations

{
  "delete_email": {
    "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

{
  "create_draft": {
    "limits": [
      {
        "counter": "create_draft_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_draft": {
    "limits": [
      {
        "counter": "get_draft_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 IMAP Email MCP Server — 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 IMAP EMAIL →

Free to start. No card required.

FULL CATALOGUE

All 10 IMAP Email MCP Server tools

DESTRUCTIVE 1 tools

Destructive delete_email Delete an email by UID

WRITE 3 tools

Write create_draft Create a new draft email Write send_email Send an email directly Write update_draft Update an existing draft by deleting old and creating new

READ 6 tools

Read get_draft Get a specific draft email by UID Read get_email Get full email content by UID Read list_drafts List all draft emails Read list_emails List emails from a folder with optional filtering Read list_folders List all email folders/mailboxes in the IMAP account Read search_emails Search emails by subject, from, or body text

EXPLORE

Related servers

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

FAQ

Questions about IMAP Email MCP Server

Can an AI agent delete data through the IMAP Email MCP Server MCP server? +

Yes. The IMAP Email MCP Server server exposes 1 destructive tools including delete_email. 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 IMAP Email MCP Server? +

The IMAP Email MCP Server server has 3 write tools including create_draft, send_email, update_draft. 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 IMAP Email MCP Server.

How many tools does the IMAP Email MCP Server MCP server expose? +

10 tools across 3 categories: Destructive, Read, Write. 6 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on IMAP Email MCP Server? +

Register the IMAP Email MCP Server 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 IMAP Email MCP Server tool call.

Deterministic rules across all 10 IMAP Email MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON IMAP EMAIL →

Free to start. No card required.

10 IMAP Email MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.