Create a new Google Docs document with a title. Returns the document ID and metadata.
AI agents use gdoc_create to create or update resources in Google Docs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Docs environment.
Creating a new document is a Write action that modifies the user's Google Docs account by adding a new document. This is reversible (can be deleted) and has no financial impact, but carries medium severity due to potential for abuse in creating numerous documents or documents with misleading content that could affect the user's account state and quota.
From the tool's definition Tool name 'gdoc_create' and description 'Create a new Google Docs document' indicate document creation, a reversible write operation.
Attacks that exploit this kind of access
Create a new Google Docs document with a title. Returns the document ID and metadata. It is categorised as a Write tool in the Google Docs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Docs MCP server in PolicyLayer and add a rule for gdoc_create: 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. Nothing to install.
gdoc_create 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 gdoc_create 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 gdoc_create. 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.
gdoc_create is provided by the Google Docs MCP server (node2flow-th/google-docs-mcp-community). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →