dns_records

Get DNS records for a domain

SERVERDomain Tools MCP Server SOURCEdeshabhishek007/domain-tools-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/deshabhishek007-domain-tools-mcp-server/dns-records.md

WHAT IT DOES

What dns_records does on Domain Tools MCP Server

AI agents call dns_records to retrieve information from Domain Tools MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why dns_records is rated Low

This tool performs a DNS query to retrieve DNS records associated with a domain. It has no side effects—it simply returns existing DNS data without creating, modifying, deleting, or executing any operations. This is a standard informational lookup, consistent with the 'Read' category for retrieval operations.

From the tool's definition The tool description explicitly states 'Get DNS records for a domain', which is a retrieval operation. DNS record queries are read-only operations that retrieve publicly available DNS information without modifying any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dns_records safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Domain Tools MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dns_records, this is the rule to start with:

dns_records Allowed

dns_records is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dns_records": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Domain Tools MCP Server, apply this rule, and every dns_records call is checked against it from then on.

FAQ

Questions about dns_records

What does the dns_records tool do? +

Get DNS records for a domain. It is categorised as a Read tool in the Domain Tools MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dns_records? +

Register the Domain Tools MCP Server MCP server in PolicyLayer and add a rule for 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 Domain Tools MCP Server. Nothing to install.

What risk level is dns_records? +

dns_records is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dns_records? +

Yes. Add a rate_limit block to the 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.

How do I block dns_records completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides dns_records? +

dns_records is provided by the Domain Tools MCP Server MCP server (deshabhishek007/domain-tools-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Domain Tools MCP Server, and thousands of servers like it.

This server

All 4 Domain Tools MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →