Create a new Google Doc
AI agents use gdrive_doc_create to create or update resources in GDrive MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GDrive MCP Server environment.
This tool creates new documents in Google Drive, which is a reversible write operation. The user can delete or modify the created document afterward. Severity is medium because misuse could result in unauthorized document creation and storage consumption, but the action is not destructive (the document can be deleted) and does not involve financial transactions or code execution.
From the tool's definition Tool name is 'gdrive_doc_create' and description states 'Create a new Google Doc'. The verb 'create' indicates the tool adds new data to Google Drive.
Attacks that exploit this kind of access
Create a new Google Doc. It is categorised as a Write tool in the GDrive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GDrive MCP Server MCP server in PolicyLayer and add a rule for gdrive_doc_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 GDrive MCP Server. Nothing to install.
gdrive_doc_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 gdrive_doc_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 gdrive_doc_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.
gdrive_doc_create is provided by the GDrive MCP Server MCP server (shaikh3/gdrive-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 →