New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

dns_add

Create a DNS record at the user's DNS provider. Uses Cloudflare API when CF_API_TOKEN is set; otherwise returns paste-at-your-registrar instructions verbatim. Owner-only; never reachable from a guest token. Returns {ok, recordId, manual, instruction?}.

SERVERYaver SOURCEyaver-cli
Medium RISK CLASS
Category Write
Parameters 74 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/dns-add.md

What dns_add does on Yaver

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

ParameterTypeRequiredDescription
ttl integer TTL seconds. 0 = auto.
name string Yes Record name relative to zone ("@" or "sub")
type string Yes
zone string Yes Apex domain — e.g. myapp.com
content string Yes IP for A/AAAA, hostname for CNAME, value for TXT
proxied boolean Cloudflare-only: route through CF proxy.
provider string Force a provider. Default auto.

Parameters from the server's own tool schema.

Why dns_add is rated Medium

Creates DNS records with lasting effects; reversible but high-impact for domain configuration and potential security implications.

From the tool's definition Create a DNS record at the user's DNS provider. Uses Cloudflare API.

Risk signalsAccepts raw HTML/template content (content)

Questions about dns_add

What does the dns_add tool do? +

Create a DNS record at the user's DNS provider. Uses Cloudflare API when CF_API_TOKEN is set; otherwise returns paste-at-your-registrar instructions verbatim. Owner-only; never reachable from a guest token. Returns {ok, recordId, manual, instruction?}. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does dns_add accept? +

dns_add accepts 7 parameters: ttl, name, type, zone, content, proxied, provider. Required: name, type, zone, content. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dns_add? +

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

What risk level is dns_add? +

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

Can I rate-limit dns_add? +

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

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

dns_add is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Yaver, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.