drive_folder_create
Create a folder inside the space. parent_id=null creates at root. color is HEX (#RRGGBB); omitted = default slate gray. is_shared=true makes it visible to every mailbox in the account immediately (must be top-level — parent_id must be null when is_shared is true).
This record as markdown: /tools/trekmail-mcp-server/drive-folder-create.md
What drive_folder_create does on TrekMail MCP Server
AI agents use drive_folder_create to create or update resources in TrekMail MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TrekMail MCP Server environment.
Why drive_folder_create is rated Medium
This is a Write operation because it creates a new folder, modifying the drive structure in a reversible manner. It doesn't delete data (Destructive), execute code (Execute), involve financial transactions (Financial), or merely retrieve data (Read).
From the tool's definition Tool name 'drive_folder_create' and description 'Create a folder inside the space' indicate folder creation, which modifies the file system state reversibly.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs drive_folder_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drive_folder_create, this is the rule to start with:
drive_folder_create 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 TrekMail MCP Server, apply this rule, and every drive_folder_create call is checked against it from then on.
Questions about drive_folder_create
Create a folder inside the space. parent_id=null creates at root. color is HEX (#RRGGBB); omitted = default slate gray. is_shared=true makes it visible to every mailbox in the account immediately (must be top-level — parent_id must be null when is_shared is true). It is categorised as a Write tool in the TrekMail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_folder_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 TrekMail MCP Server. Nothing to install.
drive_folder_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 drive_folder_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 drive_folder_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.
drive_folder_create is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TrekMail MCP Server, and thousands of servers like it.
This server
Across the catalogue