get_domain_branding

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/get-domain-branding.md

WHAT IT DOES

What get_domain_branding does on TrekMail MCP Server

AI agents call get_domain_branding to retrieve information from TrekMail MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_domain_branding is rated Low

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

RECOMMENDED RULE

The rule that runs get_domain_branding 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 get_domain_branding, this is the rule to start with:

get_domain_branding Allowed

get_domain_branding is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_domain_branding": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every get_domain_branding call is checked against it from then on.

FAQ

Questions about get_domain_branding

What does the get_domain_branding tool do? +

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.

How do I enforce a policy on get_domain_branding? +

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.

What risk level is get_domain_branding? +

get_domain_branding is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_domain_branding? +

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.

How do I block get_domain_branding completely? +

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.

What MCP server provides get_domain_branding? +

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.

KEEP EXPLORING

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

This server

All 248 TrekMail MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →