convert_shared_mailbox_to_regular
Convert a shared (team) mailbox back to a regular user mailbox. ALL existing memberships, Webmail access, and delegated native IMAP access are revoked, then direct login is re-enabled with the supplied password. A retryable
This record as markdown: /tools/trekmail-mcp-server/convert-shared-mailbox-to-regular.md
What convert_shared_mailbox_to_regular does on TrekMail MCP Server
AI agents use convert_shared_mailbox_to_regular 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_shared_mailbox_to_regular is rated Medium
While the tool modifies mailbox configuration and access controls significantly, these changes are reversible. Memberships can be re-added, access can be re-granted, and the mailbox itself is not deleted. This is a Write operation (modifies configuration state) rather than Destructive (which would be irreversible deletion/data loss).
From the tool's definition Tool converts a shared mailbox to a regular user mailbox, which involves revoking existing memberships and Webmail access, then re-enabling direct login with a supplied password.
Attacks that exploit this kind of access
The rule that runs convert_shared_mailbox_to_regular 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_shared_mailbox_to_regular, this is the rule to start with:
convert_shared_mailbox_to_regular 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_shared_mailbox_to_regular call is checked against it from then on.
Questions about convert_shared_mailbox_to_regular
Convert a shared (team) mailbox back to a regular user mailbox. ALL existing memberships, Webmail access, and delegated native IMAP access are revoked, then direct login is re-enabled with the supplied password. A retryable. 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_shared_mailbox_to_regular: 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_shared_mailbox_to_regular 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_shared_mailbox_to_regular 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_shared_mailbox_to_regular. 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_shared_mailbox_to_regular 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