// SCAN REPORT

Imap

12 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

2 can modify or destroy data

10 read-only

12 tools total

Community server · catalogue entry verified 03/07/2026

How to control Imap ↓

TOOL MAP

What Imap exposes to your agents

Read (10) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Imap tools

Write · High create_message Creating messages (drafts) in an email system is a write operation—it creates new data (email drafts) that can be sent or further modified. Write · Medium change_keywords The tool name and server description both reference keyword management, implying this tool modifies keyword metadata on email messages.

2 of Imap's 12 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

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

Rate limit write operations

{
  "change_keywords": {
    "limits": [
      {
        "counter": "change_keywords_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_header": {
    "limits": [
      {
        "counter": "get_header_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 — 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 →

Instant setup, no code required.

FULL CATALOGUE

All 12 Imap tools

WRITE 2 tools

Write change_keywords change_keywords Write create_message create_message

READ 10 tools

Read get_header Read message header for the given uid in directory Read get_header_field Read a message header field for the given uid in directory Read get_html Read HTML body for the given uid in directory Read get_keywords get_keywords Read get_size Read message size for the given uid in directory Read get_text Read plain text body for the given uid in directory Read list_mailboxes list_mailboxes Read mailboxes_status Get the status of a mailbox Read search search Read whoami Returns the configured email address for the current account.

FAQ

Questions about Imap

How do I prevent bulk modifications through Imap? +

The Imap server has 2 write tools including change_keywords, create_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 Imap.

How many tools does the Imap MCP server expose? +

12 tools across 2 categories: Read, Write. 10 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Imap? +

Register the Imap 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 tool call.

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

ENFORCE POLICY ON IMAP →

Instant setup, no code required.

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