Check domain availability with pricing. Final validation before registration. Best practices: - Input must be a fully qualified domain name including TLD (e.g., 'example.com', not just 'example'). - If status='available': present reg_url and price clearly. If price is significantly higher than st...
Part of the DomainKits server.
Free to start. No card required.
AI agents call available to retrieve information from DomainKits without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though available only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"available": {}
}
}See the full DomainKits policy for all 38 tools.
These attack patterns abuse exactly the kind of access available gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Check domain availability with pricing. Final validation before registration. Best practices: - Input must be a fully qualified domain name including TLD (e.g., 'example.com', not just 'example'). - If status='available': present reg_url and price clearly. If price is significantly higher than standard registration (~$10-15 for .com), flag it as a premium/reserved domain — the registry is charging a premium price. - If status='registered': state clearly the domain is taken. Do not automatically suggest alternatives — let the user decide if they want to explore other options. - If status='expiring': domain is in the expiration pipeline — can be backordered via reg_url, not directly registered. - If status='reserved': registry-reserved domain — not available for registration. - If status='unknown': check was inconclusive — do not assume available or unavailable. - For batch checking multiple domains, use bulk_available instead — it checks up to 10 at once. - This tool is the definitive availability check. Other tools (tld_check, deleted, expired) may show signals of availability, but only this tool or bulk_available confirms registrability and returns actual pricing. - Disclose affiliate links when aff=true.. It is categorised as a Read tool in the DomainKits MCP Server, which means it retrieves data without modifying state.
Register the DomainKits MCP server in PolicyLayer and add a rule for available: 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 DomainKits. Nothing to install.
available 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 available 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 available. 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.
available is provided by the DomainKits MCP server (https://api.domainkits.com/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 38 DomainKits tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.