apply_cloudflare_dns · TrekMail MCP Server MCP

WHAT IT DOES

What apply_cloudflare_dns does on TrekMail MCP Server

AI agents use apply_cloudflare_dns 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 apply_cloudflare_dns needs a policy

Creating DNS records is a reversible write operation that modifies email infrastructure configuration. While DNS changes can have significant consequences (disrupting email delivery if misconfigured), they are not inherently destructive since records can be modified or deleted afterward. The tool is designed for infrastructure management rather than data deletion.

From the tool's definition The tool description explicitly states it 'Creates MX, SPF, DKIM, DMARC records automatically' via the Cloudflare API. These are DNS record modifications that persist in the domain's DNS configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

apply_cloudflare_dns Rate-limited

apply_cloudflare_dns 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": {
    "apply_cloudflare_dns": {
      "limits": [
        {
          "counter": "apply_cloudflare_dns_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 apply_cloudflare_dns

What does the apply_cloudflare_dns tool do? +

Apply DNS record changes via Cloudflare API. Creates MX, SPF, DKIM, DMARC records automatically. Use preview first to see what will change. 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 apply_cloudflare_dns? +

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

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

Can I rate-limit apply_cloudflare_dns? +

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

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

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