whoisjson.dns.subdomains
Discover subdomains for any domain via DNS brute-force enumeration. Returns subdomain names, DNS record types (A/CNAME/MX), resolved IPs, and active/inactive status. Useful for security reconnaissance, asset inventory, and infrastructure mapping (WhoisJSON)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/whoisjson.dns.subdomains.md
What whoisjson.dns.subdomains does on Apibase
AI agents call whoisjson.dns.subdomains 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 discover subdomains (e.g. github.com, example.com) |
Parameters from the server's own tool schema.
Why whoisjson.dns.subdomains is rated Low
Queries and retrieves DNS subdomain data without modifying systems, but enables reconnaissance with elevated risk.
From the tool's definition Discover subdomains via DNS brute-force enumeration, returns subdomain names, DNS record types, resolved IPs.
Attacks that exploit this kind of access
The rule that runs whoisjson.dns.subdomains 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 whoisjson.dns.subdomains, this is the rule to start with:
whoisjson.dns.subdomains 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 Apibase, apply this rule, and every whoisjson.dns.subdomains call is checked against it from then on.
Questions about whoisjson.dns.subdomains
Discover subdomains for any domain via DNS brute-force enumeration. Returns subdomain names, DNS record types (A/CNAME/MX), resolved IPs, and active/inactive status. Useful for security reconnaissance, asset inventory, and infrastructure mapping (WhoisJSON). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
whoisjson.dns.subdomains accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for whoisjson.dns.subdomains: 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.
whoisjson.dns.subdomains 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 whoisjson.dns.subdomains 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 whoisjson.dns.subdomains. 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.
whoisjson.dns.subdomains 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.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue