AI agents call get_dns_records to retrieve information from Domain-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves DNS records, which is a read-only query operation. DNS records are typically public information accessible via standard DNS queries. No data is modified, deleted, or executed. The tool has minimal blast radius if misused—it only exposes publicly available information that can already be queried through public DNS infrastructure.
From the tool's definition Tool name 'get_dns_records' and description 'Get all DNS records for a domain' indicate retrieval of publicly available DNS information with no modification or execution of commands.
Documented attack patterns abuse exactly the kind of access get_dns_records gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Domain-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dns_records:
{
"version": "1",
"default": "deny",
"tools": {
"get_dns_records": {}
}
}get_dns_records is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all DNS records for a domain. It is categorised as a Read tool in the Domain-MCP MCP Server, which means it retrieves data without modifying state.
Register the Domain- MCP server in PolicyLayer and add a rule for get_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-MCP. Nothing to install.
get_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 get_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 get_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.
get_dns_records is provided by the Domain- MCP server (rinadelph/domain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Domain-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Domain-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.