set_domain_brand_logo
Upload a brand asset for a domain, base64-encoded. slot=light is the logo for light backgrounds, slot=dark for dark backgrounds, slot=favicon is the browser-tab icon. content_base64 is the raw image bytes base64-encoded — PNG or JPG (favicon also accepts ICO), max 1 MB; SVG is not supported. Conf...
This record as markdown: /tools/trekmail-mcp-server/set-domain-brand-logo.md
What set_domain_brand_logo does on TrekMail MCP Server
AI agents use set_domain_brand_logo 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.
Why set_domain_brand_logo is rated Medium
The tool modifies domain branding configuration by uploading logo assets. While it has a guard requiring TREKMAIL_ALLOW_DESTRUCTIVE, the actual operation is reversible (logos can be re-uploaded or deleted via separate tools). This is a Write operation: it creates/modifies data without permanent destruction.
From the tool's definition Upload a brand asset for a domain, base64-encoded... content_base64 is the raw image bytes base64-encoded. This tool creates or modifies domain branding assets, which are reversible changes to configuration data.
Attacks that exploit this kind of access
The rule that runs set_domain_brand_logo 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 set_domain_brand_logo, this is the rule to start with:
set_domain_brand_logo 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.
The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every set_domain_brand_logo call is checked against it from then on.
Questions about set_domain_brand_logo
Upload a brand asset for a domain, base64-encoded. slot=light is the logo for light backgrounds, slot=dark for dark backgrounds, slot=favicon is the browser-tab icon. content_base64 is the raw image bytes base64-encoded — PNG or JPG (favicon also accepts ICO), max 1 MB; SVG is not supported. Configure branding (set_domain_branding) before uploading. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true. 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.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for set_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.
set_domain_brand_logo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_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 set_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.
set_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.
This server
Across the catalogue