Check how many TLDs have specific keywords registered. Batch-compare keyword popularity by cross-TLD registration distribution. Best practices: - Use comma-separated keywords for side-by-side comparison (max 10): keywords='ai,tech,cloud,smart'. This is the tool's core strength — comparing relativ...
Part of the DomainKits server.
Free to start. No card required.
AI agents call bulk_tld 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 bulk_tld 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": {
"bulk_tld": {}
}
}See the full DomainKits policy for all 38 tools.
These attack patterns abuse exactly the kind of access bulk_tld 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 how many TLDs have specific keywords registered. Batch-compare keyword popularity by cross-TLD registration distribution. Best practices: - Use comma-separated keywords for side-by-side comparison (max 10): keywords='ai,tech,cloud,smart'. This is the tool's core strength — comparing relative popularity across multiple keywords in one call. - Interpreting total count: 100+ TLDs registered = highly competitive, well-known keyword. 50-100 = moderate popularity. 20-50 = niche but recognized. <20 = low market interest or very new concept. - The popular vs cctld vs other breakdown reveals the keyword's reach: high popular count (com/net/org/io/ai) = commercially validated. High cctld count = global brand interest or defensive registration. High other count = speculative gTLD registrations. - Use this to compare synonyms or variations before deciding which keyword to invest in — e.g., compare 'automate' vs 'automation' vs 'autoflow' to see which has stronger market validation. - Pairs well with tld_check for drilling into a single keyword's full TLD-by-TLD breakdown after identifying winners here.. 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 bulk_tld: 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.
bulk_tld 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 bulk_tld 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 bulk_tld. 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.
bulk_tld 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.