create_shared_mailbox
Create a new shared (team) mailbox. The mailbox has no direct login; members use their own regular mailbox credentials in Webmail and, when enabled, delegated native IMAP/SMTP access. All members can read and can send as the shared address by default. Optionally use shared account storage or supp...
This record as markdown: /tools/trekmail-mcp-server/create-shared-mailbox.md
What create_shared_mailbox does on TrekMail MCP Server
AI agents use create_shared_mailbox 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 create_shared_mailbox is rated Medium
Creating a shared mailbox is a reversible Write operation that establishes new email infrastructure and modifies the system state. While it has broad organizational impact (affects team messaging, delegated access, and storage allocation), it is not destructive (can be deleted), not financial, and does not execute arbitrary code.
From the tool's definition Tool name and description explicitly state 'Create a new shared (team) mailbox' — this creates new infrastructure and messaging resources within the email system.
Attacks that exploit this kind of access
The rule that runs create_shared_mailbox 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 create_shared_mailbox, this is the rule to start with:
create_shared_mailbox 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 create_shared_mailbox call is checked against it from then on.
Questions about create_shared_mailbox
Create a new shared (team) mailbox. The mailbox has no direct login; members use their own regular mailbox credentials in Webmail and, when enabled, delegated native IMAP/SMTP access. All members can read and can send as the shared address by default. Optionally use shared account storage or supply storage_mb for a dedicated allocation. 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 create_shared_mailbox: 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.
create_shared_mailbox 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_shared_mailbox 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_shared_mailbox. 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_shared_mailbox 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