gTLD rankings by registration volume. See which gTLDs have the most new registrations today or the most total active domains. Best practices: - type='newly' ranks by today's new registrations — useful for spotting which TLDs are currently hot. Sudden spikes in a usually quiet TLD may signal a pro...
Part of the DomainKits server.
Free to start. No card required.
AI agents call tld_rank 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 tld_rank 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": {
"tld_rank": {}
}
}See the full DomainKits policy for all 38 tools.
These attack patterns abuse exactly the kind of access tld_rank 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.
gTLD rankings by registration volume. See which gTLDs have the most new registrations today or the most total active domains. Best practices: - type='newly' ranks by today's new registrations — useful for spotting which TLDs are currently hot. Sudden spikes in a usually quiet TLD may signal a promotion or speculative wave. - type='active' ranks by total active domain count — reflects overall market size and maturity. - Compare newly vs active to find TLDs with disproportionate registration activity relative to their size (high new-to-active ratio = momentum signal). - type='newly' data has a one-day lag — it reflects yesterday's registrations, not today's. - The key insight from newly rankings is relative change, not absolute numbers. A TLD jumping significantly in rank or showing unusual registration volume compared to its typical level is the signal worth investigating — use tld_trends for historical baseline and web_search to identify the cause. - This data pairs well with tld_trends: tld_rank shows today's snapshot, tld_trends shows the trajectory over time.. 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 tld_rank: 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.
tld_rank 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 tld_rank 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 tld_rank. 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.
tld_rank 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.