// SCAN REPORT

Mailgent MCP Server

45 tools. 26 can modify or destroy data without limits.

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

Last updated: 3 Jul 2026

26 can modify or destroy data

19 read-only

45 tools total

Community server · catalogue entry verified 03/07/2026

How to control Mailgent MCP Server ↓

TOOL MAP

What Mailgent MCP Server exposes to your agents

Read (19) Write / Execute (16) Destructive / Financial (10)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Mailgent MCP Server tools

Financial · Critical payments_pay This tool executes irreversible financial transactions by paying USDC to URLs, directly committing financial obligations. Financial · High payments_mandates_create Creating a spend/payment mandate defines financial authorization rules (spending limits, approved payees, recurring payment permissions) for an identity. Financial · High payments_activity The tool surfaces financial payment data (bank-statement-style feed of payments sent), placing it firmly in the Financial category. Destructive · High mail_delete_thread This tool permanently deletes email data (an entire thread and all associated messages).

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

POLICY

How to control Mailgent MCP Server

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

Block financial tools by default

{
  "payments_activity": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations

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

{
  "calendar_create": {
    "limits": [
      {
        "counter": "calendar_create_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "calendar_get": {
    "limits": [
      {
        "counter": "calendar_get_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 Mailgent 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 MAILGENT →

Instant setup, no code required.

FULL CATALOGUE

All 45 Mailgent MCP Server tools

FINANCIAL 3 tools

Financial payments_activity Bank-statement-style merged feed of payments sent (direction: Financial payments_mandates_create Create the spend policy for this identity Financial payments_pay Pay an x402-priced URL in USDC under this identity

DESTRUCTIVE 7 tools

Destructive calendar_delete Delete a calendar event Destructive identities_delete Permanently delete an identity and all its data (inbox, vault, logs) Destructive mail_delete_message Delete a single message from the inbox Destructive mail_delete_rule Delete an email allow/block rule by its ID Destructive mail_delete_thread Delete an entire thread and all its messages Destructive payments_mandates_revoke Revoke a mandate. The on-chain session key is not uninstalled (manual via Console if needed); settled payments Destructive vault_delete Remove a credential from the vault

EXECUTE 1 tools

Execute identity_sign Sign arbitrary data with this identity

WRITE 15 tools

Write calendar_create Create a new event on this identity Write calendar_set_public Make this identity Write calendar_update Update an existing calendar event Write identities_create Create a new agent identity. All fields default — call with Write identities_update Rename an identity. The inbox email address is immutable; only the display name can change. For scope changes, Write identities_update_scopes Add or remove scopes from an identity Write mail_add_rule Add an allow or block rule for email. Use type ALLOW or BLOCK, scope RECEIVE/SEND/REPLY, and value as email or Write mail_reply Reply to an existing email in a thread Write mail_send Send an email from your agent Write mail_update_labels Add or remove labels on a message Write mail_update_thread_labels Add or remove labels on a thread (e.g. Write vault_store Store or update an encrypted credential in the vault. Prefer the typed helpers (vault_storeApiKey, vault_store Write vault_storeApiKey Store an API_KEY credential. Use just Write vault_storeCard Store a payment card as an encrypted credential. This is password-manager-style secret storage — the vault doe Write vault_storeShippingAddress Store a shipping / mailing address as an encrypted credential.

READ 19 tools

Read calendar_get Get details of a specific calendar event Read calendar_list List events on this identity Read identities_get Get details of a specific identity Read identities_list List all identities in the organization Read identities_rotate_key Generate a new API key for an identity. The old key is immediately invalidated. Read identity_verify Verify a signature against any did:web identity. Resolves the DID Document and checks the Ed25519 signature. Read identity_whoami Get your agent identity info — name, email, DID, scopes, and purpose (SELLER or BUYER) Read mail_get_attachment Download the contents of an email attachment as base64-encoded data. Use mail_get_message or mail_get_thread f Read mail_get_message Get a specific email by its messageId Read mail_get_thread Get a full email thread with messages (newest 200 by default) Read mail_list_messages List emails in your agent Read mail_list_rules List all allow/block rules for this identity Read mail_list_threads List email threads in your agent Read payments_mandates_get Fetch one mandate by id, with live spend counters. Read payments_mandates_list List spend mandates attached to this identity Read vault_get Retrieve a decrypted credential from the vault. For TOTP credentials, use vault_totp instead to get the code. Read vault_list List all credentials in the vault (metadata only, no secrets) Read vault_totp Generate the current 6-digit TOTP code. Works on any credential that has a TOTP secret. Response also includes Read vault_totp_use_backup Atomically consume one single-use TOTP backup code. The popped code is moved into data.usedBackupCodes for aud

EXPLORE

Related servers

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

FAQ

Questions about Mailgent MCP Server

Can an AI agent move money through the Mailgent MCP Server MCP server? +

Yes. The Mailgent MCP Server server exposes 3 financial tools including payments_activity, payments_mandates_create, payments_pay. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

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

Yes. The Mailgent MCP Server server exposes 7 destructive tools including calendar_delete, identities_delete, mail_delete_message. 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 Mailgent MCP Server? +

The Mailgent MCP Server server has 15 write tools including calendar_create, calendar_set_public, calendar_update. 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 Mailgent MCP Server.

How many tools does the Mailgent MCP Server MCP server expose? +

45 tools across 4 categories: Destructive, Financial, Read, Write. 19 are read-only. 26 can modify, create, or delete data.

How do I enforce a policy on Mailgent MCP Server? +

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

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

ENFORCE POLICY ON MAILGENT →

Instant setup, no code required.

45 Mailgent MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.