domains.get_dns_hosts
List DNS host records for one domain this Vee3 account manages. Use for managed Namecheap DNS only. For public DNS lookup of any domain, use domains.dns_records instead. Cost = 3 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/domains.get-dns-hosts.md
What domains.get_dns_hosts does on Vee3
AI agents call domains.get_dns_hosts to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Managed domain name (for example example.com). |
Parameters from the server's own tool schema.
Why domains.get_dns_hosts is rated Low
Tool retrieves DNS records from managed domains; no modification or side effects.
From the tool's definition List DNS host records for one domain this Vee3 account manages.
Attacks that exploit this kind of access
The rule that runs domains.get_dns_hosts 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.get_dns_hosts, this is the rule to start with:
domains.get_dns_hosts is read-only, so it stays allowed. 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.get_dns_hosts call is checked against it from then on.
Questions about domains.get_dns_hosts
List DNS host records for one domain this Vee3 account manages. Use for managed Namecheap DNS only. For public DNS lookup of any domain, use domains.dns_records instead. Cost = 3 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
domains.get_dns_hosts accepts 1 parameter: domain. Required: domain. 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.get_dns_hosts: 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.get_dns_hosts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the domains.get_dns_hosts 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.get_dns_hosts. 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.get_dns_hosts 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