// SCAN REPORT

Google

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

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

Last updated: 29 Jun 2026

44 can modify or destroy data

20 read-only

64 tools total

Community server · catalogue entry verified 29/06/2026

How to control Google ↓

TOOL MAP

What Google exposes to your agents

Read (20) Write / Execute (40) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Google tools

Destructive · High calendar_delete_calendar Deleting a calendar is an irreversible action that destroys all associated data. Destructive · High cancel_operation Cancelling a pending operation is irreversible in most contexts — once an email send, file share, calendar event creation, or bulk operation is cancelled, the pending action is aborted and cannot be recovered. Destructive · High gmail_delete_message Deleting email messages is irreversible and represents data loss. Destructive · High google_auth_revoke Revoking authentication and clearing credentials is a destructive operation that cannot be easily undone—the agent loses access to Google services and stored credentials are permanently removed.

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

POLICY

How to control Google

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

Deny destructive operations

{
  "calendar_delete_calendar": {
    "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_calendar": {
    "limits": [
      {
        "counter": "calendar_create_calendar_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "calendar_get_free_busy_info": {
    "limits": [
      {
        "counter": "calendar_get_free_busy_info_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 Google — 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 GOOGLE →

Instant setup, no code required.

FULL CATALOGUE

All 64 Google tools

DESTRUCTIVE 4 tools

Destructive calendar_delete_calendar Delete a calendar Destructive cancel_operation ❌ Cancel any pending operation (email, file share, calendar event, bulk operation) Destructive gmail_delete_message Delete a Gmail message (move to trash) Destructive google_auth_revoke Revoke Google authentication and clear stored credentials

EXECUTE 2 tools

Execute confirm_bulk_modify ✅ Confirm and execute the prepared bulk email operation Execute smart_forward_email_unsafe ⚠️ UNSAFE: Forward email immediately without confirmation (use names or emails)

WRITE 38 tools

Write calendar_create_calendar Create a new calendar Write calendar_create_event Create a Google Calendar event Write calendar_duplicate_event Duplicate an event to a new date/time Write calendar_respond_to_event Respond to an event invitation (accepted, declined, tentative) Write calendar_set_event_reminders Set reminders for an event (JSON format: [{"method": "email", "minutes": 30}]) Write confirm_create_event ✅ Confirm and create the prepared calendar event Write confirm_send_email ✅ Confirm and send the prepared email Write confirm_share_file ✅ Confirm and share the prepared file Write create_meeting_from_email Parse an email and create a calendar event from it Write drive_copy_file Copy a file in Google Drive Write drive_create_file Create a file in Google Drive Write drive_create_folder Create a folder in Google Drive Write drive_create_google_doc Create a Google Doc Write drive_create_google_sheet Create a Google Sheet Write drive_create_google_slide Create a Google Slides presentation Write drive_move_file Move a file to a different folder in Google Drive Write drive_rename_file Rename a file in Google Drive Write drive_share_file Share a file with a user Write drive_update_file_content Update the content of an existing file in Google Drive Write drive_upload_file Upload a file to Google Drive Write gmail_add_label Add labels to a Gmail message (comma-separated label IDs) Write gmail_archive_message Archive a Gmail message Write gmail_bulk_modify gmail_bulk_modify Write gmail_create_draft Create a Gmail draft Write gmail_forward_message Forward a Gmail message Write gmail_remove_label Remove labels from a Gmail message (comma-separated label IDs) Write gmail_reply_to_message Reply to a Gmail message Write gmail_send_html_message Send an HTML Gmail message Write gmail_send_message Send a Gmail message Write prepare_bulk_modify prepare_bulk_modify Write prepare_create_event ✅ SAFE: Prepare calendar event - shows preview and requires confirmation Write prepare_send_email ✅ SAFE: Prepare email for sending - shows preview and requires confirmation Write prepare_share_file ✅ SAFE: Prepare file sharing - shows preview and requires confirmation Write save_email_to_drive Save an email as a file in Google Drive Write share_drive_file_via_email Share a Drive file and send email notification Write smart_create_event_unsafe ⚠️ UNSAFE: Create calendar event immediately without confirmation (use names or emails) Write smart_send_email_unsafe ⚠️ UNSAFE: Send email immediately without confirmation (use names or emails) Write smart_share_file_unsafe ⚠️ UNSAFE: Share file immediately without confirmation (use names or emails)

READ 20 tools

Read calendar_get_free_busy_info Check free/busy information for calendars (comma-separated calendar IDs) Read calendar_list_calendars List available Google Calendars Read calendar_list_events List Google Calendar events Read calendar_search_events Search events by text content Read contacts_debug Debug contacts API connection and permissions Read contacts_get Get detailed contact information Read contacts_list List all contacts Read contacts_resolve_email Resolve a contact name to email address Read contacts_search Search contacts by name or email using improved searchContacts API Read contacts_search_all Search both personal contacts and directory (comprehensive search) Read contacts_search_directory Search organization directory (Google Workspace accounts only) Read drive_get_file Get file metadata and content from Google Drive Read drive_get_file_permissions Get file sharing permissions Read drive_list_files List files in Google Drive Read drive_list_shared_drives List available shared drives Read gmail_get_message Get a specific Gmail message Read gmail_list_drafts List Gmail drafts Read gmail_list_messages List Gmail messages Read google_auth_status Check Google authentication status and user info Read unified_search Search across Gmail, Drive, and Calendar with a single query

EXPLORE

Related servers

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

FAQ

Questions about Google

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

Yes. The Google server exposes 4 destructive tools including calendar_delete_calendar, cancel_operation, gmail_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 Google? +

The Google server has 38 write tools including calendar_create_calendar, calendar_create_event, calendar_duplicate_event. 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 Google.

How many tools does the Google MCP server expose? +

64 tools across 3 categories: Destructive, Read, Write. 20 are read-only. 44 can modify, create, or delete data.

How do I enforce a policy on Google? +

Register the Google 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 Google tool call.

Deterministic rules across all 64 Google tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GOOGLE →

Instant setup, no code required.

64 Google tools catalogued and risk-classified — across an index of 43,000+ MCP servers.