create_dns_record · Cloudflare Control MCP: Risk & Policy

WHAT IT DOES

What create_dns_record does on Cloudflare Control

AI agents use create_dns_record to create or update resources in Cloudflare Control — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cloudflare Control environment.

WHY IT NEEDS A POLICY

Why create_dns_record needs a policy

This tool creates DNS records, which is a Write operation—it modifies infrastructure state reversibly. Severity is high because misconfigured DNS records can redirect traffic, enable phishing, or cause service disruptions affecting multiple domains and users, though the action itself is reversible through deletion.

From the tool's definition Tool name 'create_dns_record' and description 'Create a new DNS record in a Cloudflare zone' indicate data creation. The tool modifies DNS infrastructure by adding new records, which is reversible via delete_dns_record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_dns_record Rate-limited

create_dns_record 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_dns_record": {
      "limits": [
        {
          "counter": "create_dns_record_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 Cloudflare Control, so you can run agents against it safely.

FAQ

Questions about create_dns_record

What does the create_dns_record tool do? +

Create a new DNS record in a Cloudflare zone. e.g., zone_id. It is categorised as a Write tool in the Cloudflare Control 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_dns_record? +

Register the Cloudflare Control MCP server in PolicyLayer and add a rule for create_dns_record: 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 Cloudflare Control. Nothing to install.

What risk level is create_dns_record? +

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

Can I rate-limit create_dns_record? +

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

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

create_dns_record is provided by the Cloudflare Control MCP server (josephtandle/cloudflare-mcp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.