verify_domain_branding_dns · TrekMail MCP Server MCP

WHAT IT DOES

What verify_domain_branding_dns does on TrekMail MCP Server

AI agents invoke verify_domain_branding_dns to trigger actions in TrekMail MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why verify_domain_branding_dns needs a policy

This tool triggers external operations: it queues a DNS verification check and initiates SSL certificate provisioning. These are side-effectful operations that interact with external infrastructure (DNS and SSL systems), fitting the Execute category. It does not delete data or move money, but it does trigger processes whose effects depend on the domain argument.

From the tool's definition Queue a DNS check + SSL provisioning for this domain

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

verify_domain_branding_dns Rate-limited

verify_domain_branding_dns stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_domain_branding_dns": {
      "limits": [
        {
          "counter": "verify_domain_branding_dns_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 verify_domain_branding_dns

What does the verify_domain_branding_dns tool do? +

Queue a DNS check + SSL provisioning for this domain. It is categorised as a Execute tool in the TrekMail MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on verify_domain_branding_dns? +

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

verify_domain_branding_dns is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit verify_domain_branding_dns? +

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

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

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