remove_shared_mailbox_member
Delegated dashboard roles need shared_mailboxes:write in addition to the mailboxes:write API grant; both mailboxes must be within the caller
This record as markdown: /tools/trekmail-mcp-server/remove-shared-mailbox-member.md
What remove_shared_mailbox_member does on TrekMail MCP Server
AI agents call remove_shared_mailbox_member to permanently remove resources in TrekMail MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_shared_mailbox_member is rated Critical
Removing a member from a shared mailbox is an irreversible access revocation action.
From the tool's definition remove shared mailbox member
Attacks that exploit this kind of access
The rule that runs remove_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 remove_shared_mailbox_member, this is the rule to start with:
remove_shared_mailbox_member is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every remove_shared_mailbox_member call is checked against it from then on.
Questions about remove_shared_mailbox_member
Delegated dashboard roles need shared_mailboxes:write in addition to the mailboxes:write API grant; both mailboxes must be within the caller. It is categorised as a Destructive tool in the TrekMail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for remove_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.
remove_shared_mailbox_member is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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.
Across the catalogue