New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_domain_brand_logo

Remove a brand asset (slot=light/dark/favicon) from a domain

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-domain-brand-logo.md

What remove_domain_brand_logo does on TrekMail MCP Server

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.

Why remove_domain_brand_logo is rated Critical

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

Questions about remove_domain_brand_logo

What does the remove_domain_brand_logo tool do? +

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.

How do I enforce a policy on remove_domain_brand_logo? +

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.

What risk level is remove_domain_brand_logo? +

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.

Can I rate-limit remove_domain_brand_logo? +

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.

How do I block remove_domain_brand_logo completely? +

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.

What MCP server provides remove_domain_brand_logo? +

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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of TrekMail MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.