// SCAN REPORT

Google Docs

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

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

Last updated: 30 Jun 2026

25 can modify or destroy data

1 read-only

26 tools total

Community server · catalogue entry verified 30/06/2026

How to control Google Docs ↓

TOOL MAP

What Google Docs exposes to your agents

Read (1) Write / Execute (18) Destructive / Financial (7)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Google Docs tools

Destructive · Medium gdoc_delete_bullets This tool removes formatting (bullets/numbering) from paragraphs, which is a destructive operation on document structure. Destructive · High gdoc_delete_content This tool deletes content from Google Docs documents, which is an irreversible operation that cannot be undone programmatically. Destructive · High gdoc_delete_footer This tool permanently removes a footer from a Google Doc without the ability to undo via the tool itself. Destructive · High gdoc_delete_header This tool irreversibly deletes document headers, which cannot be undone through the tool itself.

25 of Google Docs's 26 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 Docs

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

Deny destructive operations

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

{
  "gdoc_create": {
    "limits": [
      {
        "counter": "gdoc_create_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "gdoc_get": {
    "limits": [
      {
        "counter": "gdoc_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 Google Docs — 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 DOCS →

Instant setup, no code required.

FULL CATALOGUE

All 26 Google Docs tools

DESTRUCTIVE 7 tools

Destructive gdoc_delete_bullets Remove bullets or numbering from paragraphs in a range. Destructive gdoc_delete_content Delete content in a range. Get indices from gdoc_get response. Destructive gdoc_delete_footer Delete a footer from the document. Get the footer ID from gdoc_get. Destructive gdoc_delete_header Delete a header from the document. Get the header ID from gdoc_get. Destructive gdoc_delete_named_range Delete a named range by ID or name. Does not delete the content, only the reference. Destructive gdoc_delete_table_column Delete a column from an existing table. Destructive gdoc_delete_table_row Delete a row from an existing table.

EXECUTE 1 tools

Execute gdoc_batch_update Send a raw batchUpdate request with any combination of operations. Use this for complex multi-step updates or

WRITE 17 tools

Write gdoc_create Create a new Google Docs document with a title. Returns the document ID and metadata. Write gdoc_create_bullets Convert paragraphs in a range to a bulleted or numbered list. Write gdoc_create_footer Create a footer in the document. Returns the footer ID for inserting content. Write gdoc_create_header Create a header in the document. Returns the header ID for inserting content. Write gdoc_create_named_range Create a named range in the document for referencing a section of content. Write gdoc_insert_inline_image Insert an image from a URL at a specific position in the document. Write gdoc_insert_page_break Insert a page break at a specific position in the document. Write gdoc_insert_section_break Insert a section break at a specific position. Write gdoc_insert_table Insert a new table at a specific position in the document. Write gdoc_insert_table_column Insert a new column in an existing table. Write gdoc_insert_table_row Insert a new row in an existing table. Write gdoc_insert_text Insert text at a specific position in the document. Use index 1 to insert at the beginning of the body. Write gdoc_merge_table_cells Merge cells in a table. Specify the top-left cell and span. Write gdoc_replace_all_text Find and replace all occurrences of text in the entire document. Write gdoc_unmerge_table_cells Unmerge previously merged cells in a table. Write gdoc_update_paragraph_style Update paragraph style (alignment, spacing, indentation, heading) for a range. Write gdoc_update_text_style Update text style (bold, italic, font, color, etc.) for a range of text. Only specified fields are changed.

READ 1 tools

Read gdoc_get Get a Google Docs document including its full content structure, headers, footers, and named ranges.

EXPLORE

Related servers

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

FAQ

Questions about Google Docs

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

Yes. The Google Docs server exposes 7 destructive tools including gdoc_delete_bullets, gdoc_delete_content, gdoc_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 Docs? +

The Google Docs server has 17 write tools including gdoc_create, gdoc_create_bullets, gdoc_create_footer. 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 Docs.

How many tools does the Google Docs MCP server expose? +

26 tools across 3 categories: Destructive, Read, Write. 1 are read-only. 25 can modify, create, or delete data.

How do I enforce a policy on Google Docs? +

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

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

ENFORCE POLICY ON GOOGLE DOCS →

Instant setup, no code required.

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