Turn off White Label branding. scope=domain (default) turns it off for this domain only; scope=all turns it off for EVERY domain in the account — branded URLs stop serving. Saved brand assets are kept as drafts and can be re-enabled later. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true.
AI agents call remove_domain_branding 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.
Although technically reversible via re-enabling, this tool's primary effect is to irreversibly disable critical branding infrastructure with potential account-wide scope. The explicit requirement for a DESTRUCTIVE flag, combined with the blast radius of disabling branding for all domains simultaneously, places this firmly in the Destructive category.
From the tool's definition Tool description explicitly states it 'Turn[s] off White Label branding' and 'turns it off for EVERY domain in the account' when scope=all. The requirement flag TREKMAIL_ALLOW_DESTRUCTIVE=true indicates the system treats this as destructive.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Turn off White Label branding. scope=domain (default) turns it off for this domain only; scope=all turns it off for EVERY domain in the account — branded URLs stop serving. Saved brand assets are kept as drafts and can be re-enabled later. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true. 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_domain_branding: 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_domain_branding 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_domain_branding 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_domain_branding. 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_domain_branding 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →