create_folder
Creates a folder (a Drive file with mimeType application/vnd.google-apps.folder) and returns its id, name, parents and webViewLink. parent_id places it inside a folder or a shared drive ('root' or omitted = My Drive top level). Drive allows several folders with the same name in the same parent — ...
This record as markdown: /tools/a1-x-tech-mcp-google-drive/create-folder.md
What create_folder does on Mcp Google Drive
AI agents use create_folder to create or update resources in Mcp Google Drive, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Drive environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | The folder name (not required to be unique, even within one parent). |
parent_id | string | — | Parent folder or shared-drive id; omitted = My Drive root. |
Parameters from the server's own tool schema.
Why create_folder is rated Medium
An AI agent can call create_folder faster than any human can review: one bad instruction and it creates or modifies resources in Mcp Google Drive by the hundred, each call as confident as the last.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs create_folder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_folder, this is the rule to start with:
create_folder 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 Mcp Google Drive, apply this rule, and every create_folder call is checked against it from then on.
Questions about create_folder
Creates a folder (a Drive file with mimeType application/vnd.google-apps.folder) and returns its id, name, parents and webViewLink. parent_id places it inside a folder or a shared drive ('root' or omitted = My Drive top level). Drive allows several folders with the same name in the same parent — search_files first if the folder might already exist, and reuse its id instead of creating a duplicate. It is categorised as a Write tool in the Mcp Google Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_folder accepts 2 parameters: name, parent_id. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Drive MCP server in PolicyLayer and add a rule for create_folder: 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 Mcp Google Drive. Nothing to install.
create_folder 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_folder 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_folder. 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_folder is provided by the Mcp Google Drive MCP server (@a1-x-tech/mcp-google-drive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Drive, and thousands of servers like it.
This server
Across the catalogue