infra.cloudflare.dns_create
⚡ ACTION: Create a new DNS record (A, AAAA, CNAME, MX, TXT) for a Cloudflare zone. Set content (IP/hostname), TTL, and CDN proxy status. Returns new record ID (Cloudflare)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/infra.cloudflare.dns-create.md
What infra.cloudflare.dns_create does on Apibase
AI agents use infra.cloudflare.dns_create to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
ttl | integer | — | TTL in seconds (1 = automatic, 60-86400 for manual) |
name | string | Yes | Record name — subdomain or "@" for root (e.g. "www", "api", "@") |
type | string | Yes | DNS record type |
content | string | Yes | Record value — IP address for A/AAAA, hostname for CNAME, text for TXT |
proxied | boolean | — | Enable Cloudflare CDN proxy (default false). True = orange cloud, hides origin IP |
zone_id | string | Yes | Cloudflare Zone ID |
priority | integer | — | Priority for MX records (e.g. 10, 20) |
Parameters from the server's own tool schema.
Why infra.cloudflare.dns_create is rated Medium
Creates DNS records reversibly with significant blast radius; misconfiguration could redirect traffic or disrupt services.
From the tool's definition Create a new DNS record for a Cloudflare zone. Set content, TTL, and proxy status.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs infra.cloudflare.dns_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For infra.cloudflare.dns_create, this is the rule to start with:
infra.cloudflare.dns_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every infra.cloudflare.dns_create call is checked against it from then on.
Questions about infra.cloudflare.dns_create
⚡ ACTION: Create a new DNS record (A, AAAA, CNAME, MX, TXT) for a Cloudflare zone. Set content (IP/hostname), TTL, and CDN proxy status. Returns new record ID (Cloudflare). It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
infra.cloudflare.dns_create accepts 7 parameters: ttl, name, type, content, proxied, zone_id, priority. Required: name, type, content, zone_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for infra.cloudflare.dns_create: 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 Apibase. Nothing to install.
infra.cloudflare.dns_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the infra.cloudflare.dns_create 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.
Set action: deny in the PolicyLayer policy for infra.cloudflare.dns_create. 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.
infra.cloudflare.dns_create is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue