create_document
Creates a new Google Doc and returns its documentId. Without markdown it calls documents.create, which accepts ONLY a title — add content afterwards with insert_text/import_markdown. With markdown, the document is created from that Markdown via Drive conversion (headings, bold/italic, links, list...
This record as markdown: /tools/a1-x-tech-mcp-google-docs/create-document.md
What create_document does on Mcp Google Docs
AI agents use create_document to create or update resources in Mcp Google Docs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Docs environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | The document title (the Drive file name). |
markdown | string | — | Initial content as Markdown; omitted = an empty document. |
Parameters from the server's own tool schema.
Why create_document is rated Medium
An AI agent can call create_document faster than any human can review: one bad instruction and it creates or modifies resources in Mcp Google Docs by the hundred, each call as confident as the last.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs create_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_document, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Docs, apply this rule, and every create_document call is checked against it from then on.
Questions about create_document
Creates a new Google Doc and returns its documentId. Without markdown it calls documents.create, which accepts ONLY a title — add content afterwards with insert_text/import_markdown. With markdown, the document is created from that Markdown via Drive conversion (headings, bold/italic, links, lists, tables and code blocks become native Docs formatting) and the result carries id (the documentId), name and mimeType. The document lands in the authorized user's My Drive root; moving or sharing it needs the Drive UI or API, which this server does not cover. It is categorised as a Write tool in the Mcp Google Docs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_document accepts 2 parameters: title, markdown. Required: title. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Docs 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 Mcp Google Docs. Nothing to install.
create_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
create_document is provided by the Mcp Google Docs MCP server (@a1-x-tech/mcp-google-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Docs, and thousands of servers like it.
This server
Across the catalogue