AI agents use drive_create_google_doc to create or update resources in Google — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google environment.
This tool creates (writes) a new Google Doc, which is a reversible operation. It does not execute arbitrary code, delete data, or move money. The severity is medium because creating documents could be abused to generate spam, phishing content, or malicious documents at scale, but the action itself is reversible through normal deletion. Confidence is high because the name and description are explicit and unambiguous.
From the tool's definition Tool name 'drive_create_google_doc' and description 'Create a Google Doc' indicate creation of a new document resource in Google Drive.
Attacks that exploit this kind of access
Create a Google Doc. It is categorised as a Write tool in the Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google MCP server in PolicyLayer and add a rule for drive_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. Nothing to install.
drive_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 drive_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 drive_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.
drive_create_google_doc is provided by the Google MCP server (robcerda/google-mcp-server). 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 →