gdrive_create_doc · Google Drive MCP Server MCP

WHAT IT DOES

What gdrive_create_doc does on Google Drive MCP Server

AI agents use gdrive_create_doc to create or update resources in Google Drive MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive MCP Server environment.

WHY IT NEEDS A POLICY

Why gdrive_create_doc needs a policy

This tool creates new documents, which is a Write operation that modifies the user's Google Drive by adding content. While reversible (documents can be deleted), it represents a material change to the system state. Severity is medium because creating blank documents has limited scope compared to modifying existing content or deleting data, and the blast radius of an agent creating unwanted documents is manageable.

From the tool's definition The tool description explicitly states 'Create a blank Google Doc' and allows moving it into a folder, which creates new data artifacts in Google Drive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gdrive_create_doc Rate-limited

gdrive_create_doc stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gdrive_create_doc": {
      "limits": [
        {
          "counter": "gdrive_create_doc_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Drive MCP Server, so you can run agents against it safely.

FAQ

Questions about gdrive_create_doc

What does the gdrive_create_doc tool do? +

Create a blank Google Doc. Optionally move it into a specific folder after creation. It is categorised as a Write tool in the Google Drive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gdrive_create_doc? +

Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for gdrive_create_doc: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Google Drive MCP Server. Nothing to install.

What risk level is gdrive_create_doc? +

gdrive_create_doc is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gdrive_create_doc? +

Yes. Add a rate_limit block to the gdrive_create_doc rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block gdrive_create_doc completely? +

Set action: deny in the PolicyLayer policy for gdrive_create_doc. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides gdrive_create_doc? +

gdrive_create_doc is provided by the Google Drive MCP Server MCP server (wagnerlabs/gdrive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.