// SCAN REPORT

Google Drive MCP Server

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

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

Last updated: 28 Jun 2026

29 can modify or destroy data

15 read-only

44 tools total

Community server · catalogue entry verified 28/06/2026

How to control Google Drive MCP Server ↓

TOOL MAP

What Google Drive MCP Server exposes to your agents

Read (15) Write / Execute (21) Destructive / Financial (8)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Google Drive MCP Server tools

Destructive · Critical drive_batch_delete Deletion of files is irreversible and cannot be undone. Destructive · High drive_delete Deletion of files cannot be undone (even if moved to trash, it is removed from the user's active file system). Destructive · High drive_file_delete_comment This tool irreversibly removes data (comments) from files, fitting the Destructive category definition. Destructive · High drive_file_delete_reply This tool permanently removes a comment reply, which cannot be undone.

29 of Google Drive MCP Server's 44 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 Drive MCP Server

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

Deny destructive operations

{
  "drive_batch_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

{
  "drive_append_text": {
    "limits": [
      {
        "counter": "drive_append_text_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "drive_batch_get_metadata": {
    "limits": [
      {
        "counter": "drive_batch_get_metadata_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 Drive 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 GOOGLE DRIVE →

Instant setup, no code required.

FULL CATALOGUE

All 44 Google Drive MCP Server tools

DESTRUCTIVE 8 tools

Destructive drive_batch_delete Delete multiple files or folders at once Destructive drive_delete Trash or delete a file Destructive drive_file_delete_comment Delete a comment from a file Destructive drive_file_delete_reply Delete a reply to a comment on a file Destructive drive_file_empty_trash Permanently delete all trashed files Destructive drive_permission_delete Remove a user Destructive drive_shared_drive_delete Delete a Shared Drive Destructive drive_versions_delete Delete a specific version of a file

WRITE 21 tools

Write drive_append_text Append plain text to an existing text file in Drive Write drive_batch_copy Copy multiple files to a destination folder Write drive_batch_move Move multiple files to a destination folder Write drive_batch_update_permissions Update permissions for multiple files at once Write drive_comment Add a comment to a file Write drive_copy Copy a file or folder to a new location Write drive_create Create file or folder Write drive_file_lock Lock or unlock a file to prevent changes (Google Workspace only) Write drive_file_move Move a file to different folder(s) Write drive_file_reply_to_comment Reply to a comment on a file Write drive_permission_add_anyone Allow anyone with the link to access a file or folder Write drive_permission_add_domain Share file or folder with everyone in a domain Write drive_permission_update Update a user Write drive_rename Rename a file or folder Write drive_restore Restore a file from the trash Write drive_share Manage file permissions Write drive_shared_drive_create Create a new Shared Drive Write drive_shared_drive_update Update a Shared Drive Write drive_shortcut_create Create a shortcut to a file or folder Write drive_star Star or unstar a file or folder Write drive_upload Upload or update file content

READ 15 tools

Read drive_batch_get_metadata Get metadata for multiple files in a single request Read drive_changes List changes in Drive Read drive_file_content Retrieve content of a Google Drive file Read drive_file_list_comments List all comments on a file Read drive_file_list_replies List all replies to a comment on a file Read drive_file_metadata Get metadata of a file Read drive_folder_children List contents of a folder Read drive_permissions_list List all permissions of a file or folder Read drive_search Search files in Google Drive Read drive_shared_drive_files List files in a Shared Drive Read drive_shared_drive_get Get metadata for a specific Shared Drive Read drive_shared_drives_list List all accessible Shared Drives Read drive_storage_breakdown Get storage usage breakdown by file type Read drive_storage_quota Get storage quota information for the user Read drive_versions_list List all versions of a file

EXPLORE

Related servers

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

FAQ

Questions about Google Drive MCP Server

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

Yes. The Google Drive MCP Server server exposes 8 destructive tools including drive_batch_delete, drive_delete, drive_file_delete_comment. 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 Drive MCP Server? +

The Google Drive MCP Server server has 21 write tools including drive_append_text, drive_batch_copy, drive_batch_move. 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 Drive MCP Server.

How many tools does the Google Drive MCP Server MCP server expose? +

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

How do I enforce a policy on Google Drive MCP Server? +

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

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

ENFORCE POLICY ON GOOGLE DRIVE →

Instant setup, no code required.

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