Check domain availability. Zero-config via RDAP/WHOIS; adds pricing if provider configured.
AI agents call check_availability to retrieve information from Domain Suite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a lookup (via RDAP/WHOIS protocol) to determine if a domain is available for registration and optionally retrieves pricing information. It has no side effects—it does not create, modify, delete, or execute any actions. It is purely informational and falls squarely into the Read category with low severity since unauthorized use poses minimal risk beyond information disclosure.
From the tool's definition Tool name 'check_availability' and description 'Check domain availability' indicates a query operation that retrieves data about domain status and pricing without modifying anything.
Attacks that exploit this kind of access
Check domain availability. Zero-config via RDAP/WHOIS; adds pricing if provider configured. It is categorised as a Read tool in the Domain Suite MCP Server, which means it retrieves data without modifying state.
Register the Domain Suite MCP server in PolicyLayer and add a rule for check_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 Domain Suite. Nothing to install.
check_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 check_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 check_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.
check_availability is provided by the Domain Suite MCP server (oso95/domain-suite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →