update_dns_record · Cloudflare Control MCP: Risk & Policy

WHAT IT DOES

What update_dns_record does on Cloudflare Control

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

DNS record updates are reversible modifications that can change domain routing, pointing traffic to different servers. While reversible (thus Write rather than Destructive), misuse could redirect traffic maliciously, disrupt services, or enable phishing. The high severity reflects the critical nature of DNS infrastructure and the blast radius of incorrect updates affecting all traffic to a domain.

From the tool's definition Tool description states 'Update an existing DNS record by record ID', indicating modification of DNS configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_dns_record Rate-limited

update_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": {
    "update_dns_record": {
      "limits": [
        {
          "counter": "update_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 update_dns_record

What does the update_dns_record tool do? +

Update an existing DNS record by record ID. e.g., record_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 update_dns_record? +

Register the Cloudflare Control MCP server in PolicyLayer and add a rule for update_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 update_dns_record? +

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

Can I rate-limit update_dns_record? +

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

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

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