add_shared_mailbox_member
Add a member to a shared (team) mailbox. All members can read incoming mail in Webmail and, when enabled, through a delegated native IMAP folder under their own login. Optionally grant
This record as markdown: /tools/trekmail-mcp-server/add-shared-mailbox-member.md
What add_shared_mailbox_member does on TrekMail MCP Server
AI agents use add_shared_mailbox_member 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 add_shared_mailbox_member is rated Medium
This tool creates or modifies a shared mailbox membership, allowing an added member to read incoming mail and access delegated IMAP folders. While it grants access rather than deleting or executing arbitrary operations, it is fundamentally a data modification action that changes the state of the system (membership roster and access permissions).
From the tool's definition Tool name 'add_shared_mailbox_member' and description 'Add a member to a shared (team) mailbox' indicates creation/modification of membership relationships. The tool modifies access control by adding a user to a mailbox, which is a reversible Write operation.
Attacks that exploit this kind of access
The rule that runs add_shared_mailbox_member 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 add_shared_mailbox_member, this is the rule to start with:
add_shared_mailbox_member 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 add_shared_mailbox_member call is checked against it from then on.
Questions about add_shared_mailbox_member
Add a member to a shared (team) mailbox. All members can read incoming mail in Webmail and, when enabled, through a delegated native IMAP folder under their own login. Optionally grant. 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 add_shared_mailbox_member: 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.
add_shared_mailbox_member 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 add_shared_mailbox_member 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 add_shared_mailbox_member. 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.
add_shared_mailbox_member 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