createDocument · Google Docs, Drive & Sheets MCP Server MCP

WHAT IT DOES

What createDocument does on Google Docs, Drive & Sheets MCP Server

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

WHY IT NEEDS A POLICY

Why createDocument needs a policy

This tool creates new data (a Google Document) reversibly. It does not execute arbitrary code, delete data, move money, or read sensitive information. The moderate severity reflects that an AI agent could create numerous unwanted documents consuming storage quota or filling a user's Drive with spam, but the action is reversible via deletion.

From the tool's definition Tool name 'createDocument' and description state it 'Creates a new empty Google Document' with optional initial text content. This is a creation operation that modifies the user's Google Drive by adding a new resource.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

createDocument Rate-limited

createDocument 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": {
    "createDocument": {
      "limits": [
        {
          "counter": "createdocument_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 Docs, Drive & Sheets MCP Server, so you can run agents against it safely.

FAQ

Questions about createDocument

What does the createDocument tool do? +

Creates a new empty Google Document. Optionally places it in a specific folder and adds initial text content. It is categorised as a Write tool in the Google Docs, Drive & Sheets 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 createDocument? +

Register the Google Docs, Drive & Sheets MCP Server MCP server in PolicyLayer and add a rule for createDocument: 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 Docs, Drive & Sheets MCP Server. Nothing to install.

What risk level is createDocument? +

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

Can I rate-limit createDocument? +

Yes. Add a rate_limit block to the createDocument 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 createDocument completely? +

Set action: deny in the PolicyLayer policy for createDocument. 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 createDocument? +

createDocument is provided by the Google Docs, Drive & Sheets MCP Server MCP server (rulords/google-docs-mcp-personal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.