imap_connect · Email MCP Server MCP: Risk & Policy

WHAT IT DOES

What imap_connect does on Email MCP Server

AI agents use imap_connect 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_connect needs a policy

Connecting to an email account establishes a persistent session/connection, which is a stateful side-effect (not purely read). It may store credentials or session state. It is reversible (can disconnect), so it falls under Write rather than Execute or Destructive. Confidence is moderate because the description is minimal and doesn't detail what side effects the connection entails.

From the tool's definition Connect to an email account

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

imap_connect Rate-limited

imap_connect 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_connect": {
      "limits": [
        {
          "counter": "imap_connect_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_connect

What does the imap_connect tool do? +

Connect to an email account. 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_connect? +

Register the Email MCP Server MCP server in PolicyLayer and add a rule for imap_connect: 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_connect? +

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

Can I rate-limit imap_connect? +

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

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

imap_connect 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.