This record as markdown: /tools/com-local-mcp-local-mcp/create-email-folder.md
What create_email_folder does on Local
AI agents use create_email_folder to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Folder name |
account | string | — | Account name (optional, uses default) |
confirm | boolean | — | Must be true to create |
Parameters from the server's own tool schema.
Why create_email_folder is rated Medium
This tool creates a new folder in Mail.app, which is a reversible write operation. It modifies the user's mailbox structure by adding a new container, but does not delete data, execute arbitrary code, move money, or cause irreversible damage.
From the tool's definition Tool name 'create_email_folder' and description 'Creates a new mailbox folder in Mail.app' explicitly describe creating a new data structure (email folder) in a mail system.
Attacks that exploit this kind of access
The rule that runs create_email_folder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_email_folder, this is the rule to start with:
create_email_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 Local, apply this rule, and every create_email_folder call is checked against it from then on.
Questions about create_email_folder
Creates a new mailbox folder in Mail.app. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_email_folder accepts 3 parameters: name, account, confirm. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for create_email_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 Local. Nothing to install.
create_email_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_email_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_email_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_email_folder is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue