Read the per-domain White Label branding state: mode (off/inherit/custom), brand identity (name, colors, logo/favicon URLs, support + sender email), the dashboard/webmail hosts with provisioning status, the White Label add-on flag, and the CNAME records that must exist for the branded hosts to go...
AI agents call get_domain_branding to retrieve information from TrekMail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries branding configuration and DNS record status with no side effects. It is informational only—users read current state to understand what DNS records exist or need to be created, but the tool itself does not create, modify, or delete anything. It falls squarely into the Read category with low severity because misuse exposes only existing configuration data.
From the tool's definition Tool description explicitly states 'Read the per-domain White Label branding state' and lists query operations: 'discover which DNS records to create', 'poll host status'. No modification, deletion, or external execution capability is described.
Attacks that exploit this kind of access
Read the per-domain White Label branding state: mode (off/inherit/custom), brand identity (name, colors, logo/favicon URLs, support + sender email), the dashboard/webmail hosts with provisioning status, the White Label add-on flag, and the CNAME records that must exist for the branded hosts to go live. Use it to discover which DNS records to create (then add them via the Cloudflare DNS tools) and to poll host status until. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_domain_branding is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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 →