imap_send_email · Email MCP Server MCP: Risk & Policy

WHAT IT DOES

What imap_send_email does on Email MCP Server

AI agents use imap_send_email 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_send_email needs a policy

Email sending modifies the email system by creating and dispatching messages. This is reversible in scope (the message can be recalled or the account cleaned up) but has significant real-world impact—sent emails reach recipients and cannot be easily unsent in practice. Severity is high because a compromised agent could send phishing emails, spam, or impersonate the user to contacts.

From the tool's definition Tool name 'imap_send_email' explicitly indicates email sending capability. Server description states the service 'enables users to read, search, and send emails across multiple accounts and providers.' Sending is a Write operation that creates new email…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

imap_send_email Rate-limited

imap_send_email 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_send_email": {
      "limits": [
        {
          "counter": "imap_send_email_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_send_email

What does the imap_send_email tool do? +

imap_send_email. 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_send_email? +

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

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

Can I rate-limit imap_send_email? +

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

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

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