convert_mailbox_to_shared
Convert an existing regular mailbox into a shared (team) mailbox. The specified members are added immediately. IMPORTANT: this rotates the mailbox password and ends direct login for the original owner. The mailbox is then accessed through members
This record as markdown: /tools/trekmail-mcp-server/convert-mailbox-to-shared.md
What convert_mailbox_to_shared does on TrekMail MCP Server
AI agents use convert_mailbox_to_shared 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 convert_mailbox_to_shared is rated Medium
This tool permanently changes the mailbox configuration (type, password, access model), which is a significant write operation. While it does not delete data, it revokes direct login for the original owner and restructures access — highly impactful but technically reversible by converting back. The blast radius is high because misuse could lock out legitimate users from their email accounts.
From the tool's definition 'rotates the mailbox password and ends direct login for the original owner' — modifies mailbox type and access credentials; members are added immediately
Attacks that exploit this kind of access
The rule that runs convert_mailbox_to_shared 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 convert_mailbox_to_shared, this is the rule to start with:
convert_mailbox_to_shared 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 convert_mailbox_to_shared call is checked against it from then on.
Questions about convert_mailbox_to_shared
Convert an existing regular mailbox into a shared (team) mailbox. The specified members are added immediately. IMPORTANT: this rotates the mailbox password and ends direct login for the original owner. The mailbox is then accessed through members. 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 convert_mailbox_to_shared: 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.
convert_mailbox_to_shared 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 convert_mailbox_to_shared 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 convert_mailbox_to_shared. 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.
convert_mailbox_to_shared 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