// SCAN REPORT

Gmail MCP Server

65 tools. 36 can modify or destroy data without limits.

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

Last updated: 4 Jul 2026

36 can modify or destroy data

29 read-only

65 tools total

Community server · catalogue entry verified 04/07/2026

How to control Gmail MCP Server ↓

TOOL MAP

What Gmail MCP Server exposes to your agents

Read (29) Write / Execute (26) Destructive / Financial (10)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Gmail MCP Server tools

Destructive · High batch_delete_messages This tool permanently removes email messages in bulk without the ability to undo the action. Destructive · High delete_draft This tool permanently deletes draft email messages, which cannot be undone. Destructive · High delete_filter This tool permanently removes email filters, which cannot be undone. Destructive · High delete_forwarding_address Deleting a forwarding address is an irreversible action that cannot be undone without reconfiguration.

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

POLICY

How to control Gmail MCP Server

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

Deny destructive operations

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

{
  "add_delegate": {
    "limits": [
      {
        "counter": "add_delegate_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_attachment": {
    "limits": [
      {
        "counter": "get_attachment_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 Gmail 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 GMAIL →

Instant setup, no code required.

FULL CATALOGUE

All 65 Gmail MCP Server tools

DESTRUCTIVE 10 tools

WRITE 26 tools

Write add_delegate Adds a delegate to the specified account Write batch_modify_messages Modify the labels on multiple messages Write create_draft Create a draft email in Gmail. Note the mechanics of the raw parameter. Write create_filter Creates a filter Write create_forwarding_address Creates a forwarding address Write create_label Create a new label Write create_send_as Creates a custom send-as alias Write insert_smime_info Insert (upload) the given S/MIME config for the specified send-as alias Write modify_message Modify the labels on a message Write modify_thread Modify the labels applied to a thread Write patch_label Patch an existing label (partial update) Write patch_send_as Patches the specified send-as alias Write send_draft Send an existing draft Write send_message Send an email message to specified recipients. Note the mechanics of the raw parameter. Write set_default_smime_info Sets the default S/MIME config for the specified send-as alias Write stop_mail_watch Stop receiving push notifications for the given user mailbox Write untrash_message Remove a message from the trash Write untrash_thread Remove a thread from the trash Write update_auto_forwarding Updates automatic forwarding settings Write update_draft update_draft Write update_imap Updates IMAP settings Write update_label Update an existing label Write update_language Updates language settings Write update_pop Updates POP settings Write update_send_as Updates a send-as alias Write update_vacation Update vacation responder settings

READ 29 tools

Read get_attachment Get a message attachment Read get_auto_forwarding Gets auto-forwarding settings Read get_delegate Gets the specified delegate Read get_draft Get a specific draft by ID Read get_filter Gets a filter Read get_forwarding_address Gets the specified forwarding address Read get_imap Gets IMAP settings Read get_label Get a specific label by ID Read get_language Gets language settings Read get_message Get a specific message by ID with format options Read get_pop Gets POP settings Read get_profile Get the current user Read get_send_as Gets the specified send-as alias Read get_smime_info Gets the specified S/MIME config for the specified send-as alias Read get_thread Get a specific thread by ID Read get_vacation Get vacation responder settings Read list_delegates Lists the delegates for the specified account Read list_drafts List drafts in the user Read list_filters Lists the message filters of a Gmail user Read list_forwarding_addresses Lists the forwarding addresses for the specified account Read list_labels List all labels in the user Read list_messages List messages in the user Read list_send_as Lists the send-as aliases for the specified account Read list_smime_info Lists S/MIME configs for the specified send-as alias Read list_threads List threads in the user Read trash_message Move a message to the trash Read trash_thread Move a thread to the trash Read verify_send_as Sends a verification email to the specified send-as alias Read watch_mailbox Watch for changes to the user

EXPLORE

Related servers

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

FAQ

Questions about Gmail MCP Server

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

Yes. The Gmail MCP Server server exposes 10 destructive tools including batch_delete_messages, delete_draft, delete_filter. 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 Gmail MCP Server? +

The Gmail MCP Server server has 26 write tools including add_delegate, batch_modify_messages, create_draft. 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 Gmail MCP Server.

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

65 tools across 4 categories: Destructive, Execute, Read, Write. 29 are read-only. 36 can modify, create, or delete data.

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

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

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

ENFORCE POLICY ON GMAIL →

Instant setup, no code required.

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