Remove a member from a shared (team) mailbox. Pass the membership row id (the
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.
Removing a member from a shared mailbox deletes the membership association. This is a destructive, non-reversible action that revokes access. The description references a 'membership row id', confirming a record deletion. Misuse by an AI agent could inadvertently remove legitimate users from shared mailboxes, disrupting team email access with no automatic recovery path.
From the tool's definition 'Remove a member from a shared (team) mailbox' — removing membership is an irreversible deletion of the membership row
Attacks that exploit this kind of access
Remove a member from a shared (team) mailbox. Pass the membership row id (the. 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.
remove_shared_mailbox_member is one line of TrekMail MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →