domains.add_dns_host
Add one DNS host record to a managed domain without replacing the full zone. Preserves existing records. The domain must use Namecheap DNS. Call domains.get_dns_hosts afterward if HostIds are needed. Cost = 5 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/domains.add-dns-host.md
What domains.add_dns_host does on Vee3
AI agents use domains.add_dns_host to create or update resources in Vee3, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vee3 environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
ttl | integer | — | TTL in seconds (60 to 60000). Defaults to 1800. |
domain | string | Yes | Managed domain name (for example example.com). |
address | string | Yes | Record value (IP, hostname, URL, or TXT content depending on type). |
mx_pref | object | — | MX preference. Required when record_type is MX or MXE. |
host_name | string | Yes | Host label to create, for example @, www, or mail. |
record_type | string | Yes | DNS record type. Supported values: A, AAAA, ALIAS, CAA, CNAME, MX, MXE, NS, TXT, URL, URL301, FRAME. |
Parameters from the server's own tool schema.
Why domains.add_dns_host is rated Medium
Creates DNS records reversibly; domain operator can modify or delete later. Medium severity due to DNS misconfiguration potential impact.
From the tool's definition Add one DNS host record to a managed domain, preserves existing records
Attacks that exploit this kind of access
The rule that runs domains.add_dns_host safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domains.add_dns_host, this is the rule to start with:
domains.add_dns_host 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 Vee3, apply this rule, and every domains.add_dns_host call is checked against it from then on.
Questions about domains.add_dns_host
Add one DNS host record to a managed domain without replacing the full zone. Preserves existing records. The domain must use Namecheap DNS. Call domains.get_dns_hosts afterward if HostIds are needed. Cost = 5 tokens. It is categorised as a Write tool in the Vee3 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
domains.add_dns_host accepts 6 parameters: ttl, domain, address, mx_pref, host_name, record_type. Required: domain, address, host_name, record_type. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for domains.add_dns_host: 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 Vee3. Nothing to install.
domains.add_dns_host 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 domains.add_dns_host 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 domains.add_dns_host. 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.
domains.add_dns_host is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue