domains.remove_dns_host
Remove one DNS host record from a managed domain by host_id. Preserves all other records. Get host_id from domains.get_dns_hosts. The domain must use Namecheap DNS. Cost = 5 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/domains.remove-dns-host.md
What domains.remove_dns_host does on Vee3
AI agents call domains.remove_dns_host to permanently remove resources in Vee3, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Managed domain name (for example example.com). |
host_id | string | Yes | Host record id from domains.get_dns_hosts. |
Parameters from the server's own tool schema.
Why domains.remove_dns_host is rated Critical
Irreversibly deletes DNS records; cannot be undone without manual restoration.
From the tool's definition Remove one DNS host record from a managed domain by host_id.
Attacks that exploit this kind of access
The rule that runs domains.remove_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.remove_dns_host, this is the rule to start with:
domains.remove_dns_host is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every domains.remove_dns_host call is checked against it from then on.
Questions about domains.remove_dns_host
Remove one DNS host record from a managed domain by host_id. Preserves all other records. Get host_id from domains.get_dns_hosts. The domain must use Namecheap DNS. Cost = 5 tokens. It is categorised as a Destructive tool in the Vee3 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
domains.remove_dns_host accepts 2 parameters: domain, host_id. Required: domain, host_id. 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.remove_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.remove_dns_host is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the domains.remove_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.remove_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.remove_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.
Across the catalogue