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?}.
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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.
An AI agent can call dns_add faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
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.
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.
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.
dns_add 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 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.
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.
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.