create_document · Google Docs MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_document does on Google Docs MCP Server

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

WHY IT NEEDS A POLICY

Why create_document needs a policy

Creating a new Google Doc is a reversible operation that modifies state by adding a new resource, but does not delete, execute arbitrary code, or move money. The severity is medium because an AI agent could create numerous unwanted documents consuming storage quota or cluttering a user's workspace, but the impact is contained and reversible (documents can be deleted).

From the tool's definition Tool name 'create_document' and description 'Create a new Google Doc' indicate creation of new data. The server description confirms it 'enables Claude to read, create, and update Google Docs', placing this in the Write category (creates data reversibly).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_document Rate-limited

create_document 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": {
    "create_document": {
      "limits": [
        {
          "counter": "create_document_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about create_document

What does the create_document tool do? +

Create a new Google Doc. It is categorised as a Write tool in the Google Docs 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 create_document? +

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

What risk level is create_document? +

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

Can I rate-limit create_document? +

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

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

create_document is provided by the Google Docs MCP Server MCP server (mackenzienolan/google-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.