create_branding_preview · TrekMail MCP Server MCP

WHAT IT DOES

What create_branding_preview does on TrekMail MCP Server

AI agents use create_branding_preview 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 IT NEEDS A POLICY

Why create_branding_preview needs a policy

An AI agent can call create_branding_preview faster than any human can review — one bad instruction and it creates or modifies resources in TrekMail MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_branding_preview Rate-limited

create_branding_preview 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_branding_preview": {
      "limits": [
        {
          "counter": "create_branding_preview_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TrekMail MCP Server, so you can run agents against it safely.

FAQ

Questions about create_branding_preview

What does the create_branding_preview tool do? +

Mint a one-time trial-preview link that shows the account dashboard running under this domain. 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.

How do I enforce a policy on create_branding_preview? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for create_branding_preview: 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 create_branding_preview? +

create_branding_preview is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_branding_preview? +

Yes. Add a rate_limit block to the create_branding_preview 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 create_branding_preview completely? +

Set action: deny in the PolicyLayer policy for create_branding_preview. 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 create_branding_preview? +

create_branding_preview 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.

// THE FULL RECORD

create_branding_preview is one line of TrekMail MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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