domains.dns_records
Fetch DNS records for a domain. Returns an array of records. Each record includes name, ttl, type (for example A, AAAA, CNAME, MX, NS, SOA, TXT), and data (record value). Optionally pass subdomain to include records for a host under the domain (for example blog for blog.example.com). Cost = 2 tok...
This record as markdown: /tools/io-github-vee3io-vee3/domains.dns-records.md
What domains.dns_records does on Vee3
AI agents call domains.dns_records 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 | Domain name to look up (for example example.com). |
subdomain | object | — | Optional subdomain label to include (for example www or blog). |
Parameters from the server's own tool schema.
Why domains.dns_records is rated Low
This tool retrieves DNS record information from a domain's DNS configuration. It has no side effects, does not modify data, execute code, or delete anything. It is a straightforward data query operation comparable to nslookup or dig commands used for DNS lookups.
From the tool's definition Tool description states it 'Fetch[es] DNS records for a domain' and 'Returns an array of records.' The action is purely retrieval with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs domains.dns_records 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.dns_records, this is the rule to start with:
domains.dns_records 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.dns_records call is checked against it from then on.
Questions about domains.dns_records
Fetch DNS records for a domain. Returns an array of records. Each record includes name, ttl, type (for example A, AAAA, CNAME, MX, NS, SOA, TXT), and data (record value). Optionally pass subdomain to include records for a host under the domain (for example blog for blog.example.com). Cost = 2 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
domains.dns_records accepts 2 parameters: domain, subdomain. 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.dns_records: 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.dns_records 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.dns_records 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.dns_records. 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.dns_records 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