Create a new blank Google Document.
AI agents use create_google_doc 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.
Creating a blank document is a Write operation—it creates new data that can be subsequently modified or deleted. The blast radius is low because a blank document has no immediate content or side effects; it is a simple, reversible operation. No data is destroyed, financial transactions are not involved, and no external code execution occurs.
From the tool's definition Tool name is 'create_google_doc' and description states it will 'Create a new blank Google Document.' This is a creation operation that generates new data reversibly.
Attacks that exploit this kind of access
Create a new blank Google Document. 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.
Register the Google Docs MCP Server MCP server in PolicyLayer and add a rule for create_google_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 Docs MCP Server. Nothing to install.
create_google_doc 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_google_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.
Set action: deny in the PolicyLayer policy for create_google_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.
create_google_doc is provided by the Google Docs MCP Server MCP server (nickweedon/google-docs-mcp-docker). 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 →