whois.domain.availability
Check if a domain name is available for registration — fast DNS check or thorough DNS+WHOIS verification (WhoisXML)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/whois.domain.availability.md
What whois.domain.availability does on Apibase
AI agents call whois.domain.availability 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 |
|---|---|---|---|
mode | string | — | Check mode: DNS_ONLY is fast, DNS_AND_WHOIS is more accurate (default DNS_AND_WHOIS) |
domain | string | Yes | Domain name to check availability for (e.g. "example.com", "mybrand.io") |
Parameters from the server's own tool schema.
Why whois.domain.availability is rated Low
Tool performs read-only queries of domain availability data without side effects or modifications.
From the tool's definition Check if a domain name is available for registration — fast DNS check or thorough DNS+WHOIS verification
Attacks that exploit this kind of access
The rule that runs whois.domain.availability 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.domain.availability, this is the rule to start with:
whois.domain.availability 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 whois.domain.availability call is checked against it from then on.
Questions about whois.domain.availability
Check if a domain name is available for registration — fast DNS check or thorough DNS+WHOIS verification (WhoisXML). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
whois.domain.availability accepts 2 parameters: mode, 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 whois.domain.availability: 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.
whois.domain.availability 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 whois.domain.availability 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 whois.domain.availability. 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.
whois.domain.availability 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