remove_shared_mailbox_member

Remove a member from a shared (team) mailbox, revoking both Webmail and delegated native IMAP access without deleting the member

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/remove-shared-mailbox-member.md

WHAT IT DOES

What remove_shared_mailbox_member does on TrekMail MCP Server

AI agents use remove_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.

RISK

Why remove_shared_mailbox_member is rated Medium

This tool modifies access control by removing a member from a shared mailbox and revoking their access. It is reversible (the member can be re-added) and does not delete any data or accounts, placing it in the Write category. Misuse could lock legitimate users out of shared mailboxes, giving it medium severity.

From the tool's definition Remove a member from a shared (team) mailbox, revoking both Webmail and delegated native IMAP access without deleting the member

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

remove_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "remove_shared_mailbox_member": {
      "limits": [
        {
          "counter": "remove_shared_mailbox_member_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about remove_shared_mailbox_member

What does the remove_shared_mailbox_member tool do? +

Remove a member from a shared (team) mailbox, revoking both Webmail and delegated native IMAP access without deleting the member. 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.

How do I enforce a policy on remove_shared_mailbox_member? +

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.

What risk level is remove_shared_mailbox_member? +

remove_shared_mailbox_member is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit remove_shared_mailbox_member? +

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.

How do I block remove_shared_mailbox_member completely? +

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.

What MCP server provides remove_shared_mailbox_member? +

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.

KEEP EXPLORING

More on TrekMail MCP Server, and thousands of servers like it.

This server

All 248 TrekMail MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →