cf_create_dns · Access MCP: Risk & Policy

WHAT IT DOES

What cf_create_dns does on Access

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

WHY IT NEEDS A POLICY

Why cf_create_dns needs a policy

This tool modifies DNS records in a production Cloudflare zone, which is a reversible write operation (records can be deleted or modified afterwards). However, it carries high severity because misconfigured DNS records can redirect traffic, disrupt services, or enable attacks—the blast radius on misconfiguration is substantial.

From the tool's definition "Create a new DNS record" and "the record goes live immediately" indicate immediate, reversible modification of DNS records. The tool writes DNS configuration data to a live production system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cf_create_dns Rate-limited

cf_create_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": {
    "cf_create_dns": {
      "limits": [
        {
          "counter": "cf_create_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 Access, so you can run agents against it safely.

FAQ

Questions about cf_create_dns

What does the cf_create_dns tool do? +

Create a new DNS record in a Cloudflare zone. Side effect: the record goes live immediately and can affect traffic routing. Use cf_dns first to check for conflicts. It is categorised as a Write tool in the Access MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cf_create_dns? +

Register the Access MCP server in PolicyLayer and add a rule for cf_create_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 Access. Nothing to install.

What risk level is cf_create_dns? +

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

Can I rate-limit cf_create_dns? +

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

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

cf_create_dns is provided by the Access MCP server (scottpedia0/access). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.