// SCAN REPORT

Google

60 tools. 47 can modify or destroy data without limits.

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

Last updated: 3 Jul 2026

47 can modify or destroy data

13 read-only

60 tools total

Community server · catalogue entry verified 03/07/2026

How to control Google ↓

TOOL MAP

What Google exposes to your agents

Read (13) Write / Execute (38) Destructive / Financial (9)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Google tools

Destructive · Medium delete_comment This tool irreversibly removes data (a comment) that cannot be undone through normal tool operations. Destructive · High delete_doc_tab This tool permanently removes a tab (and its contents) from a Google Doc, which cannot be undone by the tool itself. Destructive · High delete_footer This tool irreversibly removes a footer from a Google Doc. Destructive · High delete_header The tool performs a delete operation on document content.

47 of Google's 60 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

{
  "delete_comment": {
    "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_comment": {
    "limits": [
      {
        "counter": "add_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "about": {
    "limits": [
      {
        "counter": "about_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 60 Google tools

DESTRUCTIVE 9 tools

Destructive delete_comment Delete a comment from a Google Drive file. Destructive delete_doc_tab Delete a tab from a Google Doc. Destructive delete_footer Delete a footer from a Google Doc. Destructive delete_header Delete a header from a Google Doc. Destructive delete_named_range Delete a named range from a Google Doc by name or ID. Destructive delete_permission Remove a permission from a Google Drive file. Destructive delete_positioned_object Delete a positioned object (e.g. floating image) from a Google Doc. Destructive delete_reply Delete a reply from a comment. Destructive trash_file Move a Google Drive file or folder to trash (or permanently delete it). Use search_drive first to find the fil

WRITE 38 tools

Write add_comment Add a comment to a Google Drive file. Optionally anchor it to quoted text. Write add_doc_tab Add a new tab to a Google Doc. Write copy_doc Copy an existing Google Doc. Optionally rename and/or move to a different folder. Write copy_file Copy any Google Drive file. Optionally rename and/or place in a specific folder. Write create_doc Create a new Google Doc with optional body text. Returns the doc ID and URL. Write create_folder Create a new folder in Google Drive. Write create_footnote Create a footnote at a position in a Google Doc. Write create_named_range Create a named range (bookmark) in a Google Doc that can be linked to. Write create_permission Share a Google Drive file with a user, group, domain, or anyone. Write create_reply Reply to a comment on a Google Drive file. Write edit_doc Edit a Google Doc in-place. Supports insert, delete, replace (find/replace all), and append. Write format_doc Format text or paragraphs in a Google Doc. Supports bold, italic, underline, strikethrough, font size/family, Write format_table Format table cells, columns, or rows in a Google Doc (borders, backgrounds, padding, widths, heights). Write insert_date Insert a date chip into a Google Doc. Write insert_image Insert an inline image into a Google Doc from a public URL. Write insert_page_break Insert a page break at a position in a Google Doc. Write insert_person Insert a person mention (@ chip) into a Google Doc. Write insert_rich_link Insert a rich link (smart chip) to a Google file into a Google Doc. Write insert_section_break Insert a section break in a Google Doc. Write insert_table Insert a table into a Google Doc. Write merge_table_cells Merge cells in a Google Doc table. Write modify_table Insert or delete rows/columns in a Google Doc table. Requires the table start index (from read_doc structure). Write move_file Move a Google Drive file or folder to a different parent folder. Write pin_table_header_rows Pin header rows in a Google Doc table. Write rename_doc Rename a Google Doc file. Write rename_doc_tab Rename a tab in a Google Doc. Use list_doc_tabs to find tab IDs. Write rename_file Rename any Google Drive file or folder. Write replace_image Replace an existing image in a Google Doc. Write replace_named_range_content Replace the content of a named range in a Google Doc (useful for templates). Write resolve_comment Resolve a comment on a Google Drive file. Write unmerge_table_cells Unmerge cells in a Google Doc table. Write update_comment Edit a comment on a Google Drive file. Write update_document_style Update page-level style of a Google Doc (margins, page size, background color). Write update_header_footer Create or replace the default header or footer in a Google Doc. Write update_list Apply or remove bulleted/numbered list formatting on a range of paragraphs in a Google Doc. Write update_named_style Update a named style (e.g. HEADING_1, NORMAL_TEXT) in a Google Doc. Write update_permission Update a permission role on a Google Drive file. Write update_section_style Update section-level style in a Google Doc (columns, margins, headers/footers).

READ 13 tools

Read about Get Google Drive account info and storage quota. Read export_doc Export a Google Doc to pdf, docx, txt, html, rtf, or epub. Read get_file_metadata Get metadata for a Google Drive file (name, type, size, owner, dates, parents, etc.). Read get_revision Get details of a specific file revision. Read list_comments List comments on a Google Drive file. Read list_doc_tabs List all tabs in a Google Doc (title, ID, index). Read list_folder List contents of a Google Drive folder. Read list_named_ranges List all named ranges (bookmarks) in a Google Doc. Read list_permissions List who has access to a Google Drive file. Read list_replies List replies on a comment. Read list_revisions List revision history of a Google Drive file. Read read_doc Read a Google Doc as plain text / markdown Read search_drive Search for files in Google Drive by name or content

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 9 destructive tools including delete_comment, delete_doc_tab, delete_footer. 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 add_comment, add_doc_tab, copy_doc. 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? +

60 tools across 3 categories: Destructive, Read, Write. 13 are read-only. 47 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 60 Google tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GOOGLE →

Instant setup, no code required.

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