whois.dns.lookup

Get DNS records for a domain — A, AAAA, MX, NS, SOA, TXT, CNAME, SRV, CAA records with TTL and raw data (WhoisXML)

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/whois.dns.lookup.md

WHAT IT DOES

What whois.dns.lookup does on Apibase

AI agents call whois.dns.lookup to retrieve information from Apibase 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 DNS records for (e.g. "google.com")
`record_type`	string	—	DNS record type to query: A, AAAA, MX, NS, SOA, TXT, CNAME, SRV, CAA, or _all (default _all)

Parameters from the server's own tool schema.

RISK

Why whois.dns.lookup is rated Low

Retrieves public DNS records; no modification, deletion, or execution capability; read-only query.

From the tool's definition Get DNS records for a domain — A, AAAA, MX, NS, SOA, TXT, CNAME, SRV, CAA records

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs whois.dns.lookup safely

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

whois.dns.lookup Allowed

whois.dns.lookup 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": {
    "whois.dns.lookup": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every whois.dns.lookup call is checked against it from then on.

FAQ

Questions about whois.dns.lookup

What does the whois.dns.lookup tool do? +

Get DNS records for a domain — A, AAAA, MX, NS, SOA, TXT, CNAME, SRV, CAA records with TTL and raw data (WhoisXML). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does whois.dns.lookup accept? +

whois.dns.lookup accepts 2 parameters: domain, record_type. Required: domain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on whois.dns.lookup? +

Register the Apibase MCP server in PolicyLayer and add a rule for whois.dns.lookup: 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 Apibase. Nothing to install.

What risk level is whois.dns.lookup? +

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

Can I rate-limit whois.dns.lookup? +

Yes. Add a rate_limit block to the whois.dns.lookup 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 whois.dns.lookup completely? +

Set action: deny in the PolicyLayer policy for whois.dns.lookup. 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 whois.dns.lookup? +

whois.dns.lookup is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

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