Remove a brand asset (slot=light/dark/favicon) from a domain
AI agents call remove_domain_brand_logo 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.
The tool removes brand assets from a domain, which is an irreversible deletion of configured branding elements (light logo, dark logo, favicon). Removing these assets cannot be undone without re-uploading the files, making this a destructive operation. The blast radius is high because it affects the visual identity of an entire domain's email infrastructure.
From the tool's definition Remove a brand asset (slot=light/dark/favicon) from a domain
Attacks that exploit this kind of access
Remove a brand asset (slot=light/dark/favicon) from a domain. 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_brand_logo: 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_brand_logo 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_brand_logo 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_brand_logo. 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_brand_logo 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 →