This record as markdown: /tools/ark7-google-drive-mcp/createtextfile.md
What createTextFile does on Google Drive
AI agents use createTextFile to create or update resources in Google Drive, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | File name (.txt or .md) |
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
content | string | Yes | File content |
parentFolderId | string | — | Parent folder ID |
Parameters from the server's own tool schema.
Why createTextFile is rated Medium
This tool creates new files reversibly in Google Drive. It is a Write operation (creates data) rather than Execute (no code/commands run), and not Destructive since file creation can be undone by deletion. The blast radius is low as creating text files has minimal downstream consequences unless an agent creates large volumes or sensitive content inadvertently.
From the tool's definition Tool name 'createTextFile' and description 'Create a new text or markdown file' indicate creation of new data in Google Drive.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs createTextFile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For createTextFile, this is the rule to start with:
createTextFile 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 Google Drive, apply this rule, and every createTextFile call is checked against it from then on.
Questions about createTextFile
Create a new text or markdown file. It is categorised as a Write tool in the Google Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
createTextFile accepts 4 parameters: name, account, content, parentFolderId. Required: name, content. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for createTextFile: 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 Drive. Nothing to install.
createTextFile 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 createTextFile 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 createTextFile. 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.
createTextFile is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
This server
Across the catalogue