// SCAN REPORT

Email Sending MCP

77 tools. 44 can modify or destroy data without limits.

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

Last updated: 10 Jun 2026

44 can modify or destroy data

33 read-only

77 tools total

Community server · catalogue entry verified 10/06/2026

How to control Email Sending MCP ↓

TOOL MAP

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

MOST DANGEROUS TOOLS

Critical Risk

Destructive · Medium cancel-email Cancelling a scheduled email is an irreversible action — once cancelled, that scheduled send is permanently aborted and cannot be undone. Destructive · High remove-api-key This tool permanently deletes an API key, which is an irreversible action that cannot be undone. Destructive · High remove-automation This tool permanently deletes automation configurations, which is an irreversible operation that cannot be recovered or restored. Destructive · High remove-broadcast This tool permanently deletes a broadcast communication that has likely been set up and potentially sent.

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

HOW TO CONTROL EMAIL SENDING MCP

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

Deny destructive operations

{
  "cancel-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

{
  "remove-contact-from-segment": {
    "limits": [
      {
        "counter": "remove-contact-from-segment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get-automation": {
    "limits": [
      {
        "counter": "get-automation_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 Email Sending MCP — 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 EMAIL SENDING →

Free to start. No card required.

ALL 77 EMAIL SENDING MCP TOOLS

DESTRUCTIVE 11 tools

Destructive cancel-email Cancel a scheduled email that has not yet been sent. Only works for emails that were scheduled using the sched Destructive remove-api-key Remove an API key by ID from Resend. Before using this tool, you MUST double-check with the user that they wan Destructive remove-automation Remove an automation by ID or Resend dashboard URL. Before using this tool, you MUST double-check with the use Destructive remove-broadcast Remove a broadcast by ID or Resend dashboard URL. Before using this tool, you MUST double-check with the user Destructive remove-contact Remove a contact from Resend (by ID or email). Before using this tool, you MUST double-check with the user tha Destructive remove-contact-property Remove a contact property by ID from Resend. Before using this tool, you MUST double-check with the user that Destructive remove-domain Remove a domain by ID from Resend. Before using this tool, you MUST double-check with the user that they want Destructive remove-segment Remove a segment by ID from Resend. Before using this tool, you MUST double-check with the user that they want Destructive remove-template Remove an email template by ID, alias, or Resend dashboard URL from Resend. Before using this tool, you MUST d Destructive remove-topic Remove a topic by ID from Resend. Before using this tool, you MUST double-check with the user that they want t Destructive remove-webhook Remove a webhook by ID from Resend. Before using this tool, you MUST double-check with the user that they want

EXECUTE 3 tools

Execute send-batch-emails Purpose: Send up to 100 transactional emails in one API call. Each item has the same fields as send-email (to, Execute send-broadcast Purpose: Send (or schedule) an existing broadcast by ID. The broadcast must have been created with create-broa Execute send-event Purpose: Fire an event to trigger automations for a specific contact. When to use: - User wants to trigger an

WRITE 30 tools

Write remove-contact-from-segment Remove a contact from a segment in Resend (by contact ID or email). Before using this tool, you MUST double-ch Write compose-broadcast Purpose: Set the TipTap JSON content of a broadcast, enabling it to be edited visually in the Resend dashboard Write compose-template Purpose: Set the TipTap JSON content of a template, enabling it to be edited visually in the Resend dashboard Write duplicate-template Duplicate an existing email template in Resend. Creates a new draft copy of the template with a new ID. Accept Write add-contact-to-segment Add a contact to a segment in Resend (by contact ID or email). Write connect-to-editor Purpose: Show agent presence in the Resend dashboard editor. Users will see an agent avatar while connected. Write create-api-key Create a new API key in Resend. The token is only shown once upon creation, so you MUST display it to the user Write create-automation Purpose: Create an automation workflow that triggers on events and executes a sequence of steps. When to use: Write create-broadcast Purpose: Create a broadcast campaign (one email sent to an entire segment). Defines subject, body, and segment Write create-contact Create a new contact in Resend. Optionally assign to segments and configure topic subscriptions. Write create-contact-property Create a new contact property in Resend. A contact property is a custom attribute (e.g. Write create-domain Create a new domain in Resend. Returns DNS records that must be configured with your DNS provider for verifica Write create-segment Create a new segment in Resend. A segment is a group of contacts that can be used to target specific broadcast Write create-template Create a new email template in Resend. Templates are created in draft status. Use publish-template to make the Write create-topic Create a new topic in Resend. Topics allow contacts to manage their subscription preferences for different typ Write create-webhook Create a new webhook in Resend. A webhook allows you to receive notifications at a specified URL when certain Write disconnect-from-editor Remove agent presence from the Resend dashboard editor. Call this when done editing. Write manage-events Purpose: Create, list, get, update, or remove event definitions in Resend. Events define named triggers that Write publish-template Publish an email template in Resend. Templates must be published before they can be used for sending emails. R Write send-email Purpose: Send a single transactional email to one or more recipients immediately (or schedule it). Use for one Write update-automation Purpose: Update an automation Write update-broadcast Update broadcast metadata by ID or Resend dashboard URL (name, subject, from, html, text, segment, preview tex Write update-contact Update a contact in Resend (by ID or email). Write update-contact-property Update an existing contact property in Resend. Only the fallback value can be changed — the key and type canno Write update-contact-topics Update topic subscriptions for a contact in Resend (by contact ID or email). Write update-domain Update an existing domain in Resend. Allows changing tracking settings, TLS mode, and capabilities. Write update-email Reschedule a scheduled email by updating its scheduled send time. Only works for emails that were scheduled an Write update-template Update template metadata by ID, alias, or Resend dashboard URL (name, subject, from, html, variables, etc.). A Write update-topic Update an existing topic in Resend. Note: defaultSubscription cannot be modified after creation. Write update-webhook Update an existing webhook in Resend. You can change the endpoint URL, subscribed events, or enable/disable th

READ 33 tools

Read get-automation Purpose: Get details of a specific automation (with its workflow) or list all automations. Modes: - With \ Read get-automation-runs Purpose: List runs for an automation, or get details of a specific run. Modes: - With \ Read get-broadcast Retrieve full details of a specific broadcast by ID or Resend dashboard URL (e.g. https://resend.com/broadcast Read get-contact Get a contact by ID or email from Resend. Read get-contact-property Get a contact property by ID from Resend. Read get-domain Get a domain by ID from Resend. Returns full domain details including DNS records needed for verification. Read get-email Retrieve full details of a specific sent transactional email by ID, including HTML and plain text content. Read get-log Purpose: Get detailed information about a specific API request log, including the full request and response bo Read get-received-email Retrieve full details of a specific received email by ID, including HTML and plain text content, headers, and Read get-received-email-attachment Retrieve details of a specific attachment from a received email, including a time-limited download URL. Read get-segment Get a segment by ID from Resend. Read get-sent-email-attachment Retrieve details of a specific attachment from a sent email, including a time-limited download URL. Read get-template Get an email template by ID, alias, or Resend dashboard URL (e.g. https://resend.com/templates/<id>) from Rese Read get-tiptap-json-content Purpose: Retrieve the existing TipTap JSON content of a broadcast or template, optionally bundled with the Tip Read get-topic Get a topic by ID from Resend. Read get-webhook Get a webhook by ID from Resend. Read list-api-keys List all API keys from Resend. Returns API key names, IDs, and creation dates. Don Read list-broadcasts Purpose: List all broadcast campaigns (newsletters/bulk emails to audiences) with ID, name, audience, status, Read list-contact-properties List all contact properties from Resend. This tool is useful for getting property IDs and seeing which custom Read list-contact-segments List all segments a contact belongs to in Resend (by contact ID or email). Don Read list-contact-topics List all topic subscriptions for a contact in Resend (by contact ID or email). Don Read list-contacts Purpose: List contacts from Resend. Optionally filter by segment. Use to discover contact IDs or emails. NOT Read list-domains List all domains from Resend. Returns domain names, statuses, regions, and capabilities. Don Read list-emails Purpose: List recently sent emails (transactional emails sent via send-email) with metadata: recipient, subjec Read list-logs Purpose: List API request logs for the account. Use to review recent API activity, debug issues, or audit API Read list-received-email-attachments List all attachments from a specific received (inbox) email. Returns attachment metadata including filename, s Read list-received-emails Purpose: List emails received (inbox) by your Resend receiving address. Use for Read list-segments Purpose: List all segments in the account. Use to get segment IDs required by create-contact, create-broadcast Read list-sent-email-attachments List all attachments from a specific sent email (from send-email or list-emails). Returns attachment metadata Read list-templates List all email templates from Resend. Returns template names, statuses, and aliases. Don Read list-topics List all topics from Resend. This tool is useful for getting topic IDs to use with other tools like send-email Read list-webhooks List all webhooks from Resend. Use to get webhook IDs and see which endpoints and events are configured. Not f Read verify-domain Trigger domain verification in Resend. This starts an asynchronous verification process that checks if the DNS

RELATED SERVERS

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

FAQ

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

Yes. The Email Sending MCP server exposes 11 destructive tools including cancel-email, remove-api-key, remove-automation. 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 Email Sending MCP? +

The Email Sending MCP server has 30 write tools including remove-contact-from-segment, compose-broadcast, compose-template. 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 Email Sending MCP.

How many tools does the Email Sending MCP server expose? +

77 tools across 4 categories: Destructive, Execute, Read, Write. 33 are read-only. 44 can modify, create, or delete data.

How do I enforce a policy on Email Sending MCP? +

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

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

ENFORCE POLICY ON EMAIL SENDING →

Free to start. No card required.

77 Email Sending MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

Email Sending MCP

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL EMAIL SENDING MCP

// ALL 77 EMAIL SENDING MCP TOOLS

// RELATED SERVERS

// FAQ