remove_white_label_member

Remove a member and revoke the API and mailbox keys they created. The membership can be restored later, but old keys never return.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/remove-white-label-member.md

WHAT IT DOES

What remove_white_label_member does on TrekMail MCP Server

AI agents call remove_white_label_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.

RISK

Why remove_white_label_member is rated Critical

Revokes keys permanently and irreversibly removes member access from white label.

From the tool's definition revoke the API and mailbox keys they created... old keys never return

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_white_label_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_white_label_member, this is the rule to start with:

remove_white_label_member Hidden

remove_white_label_member is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_white_label_member"
  ]
}

RESTRICT 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_white_label_member call is checked against it from then on.

FAQ

Questions about remove_white_label_member

What does the remove_white_label_member tool do? +

Remove a member and revoke the API and mailbox keys they created. The membership can be restored later, but old keys never return. 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.

How do I enforce a policy on remove_white_label_member? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for remove_white_label_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_white_label_member? +

remove_white_label_member is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_white_label_member? +

Yes. Add a rate_limit block to the remove_white_label_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_white_label_member completely? +

Set action: deny in the PolicyLayer policy for remove_white_label_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_white_label_member? +

remove_white_label_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 285 TrekMail MCP Server tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →