gTLD registration trends over time. Analyze historical registration patterns for specific gTLDs — spot hype cycles, compare competing extensions, or check long-term health. Two modes: - action='data' + tld (single TLD): deep-dive into one TLD's trend over time. Use this to answer 'is .ai still ho...
Part of the DomainKits server.
Free to start. No card required.
AI agents invoke tld_trends to trigger processes or run actions in DomainKits. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
tld_trends can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"tld_trends": {
"limits": [
{
"counter": "tld_trends_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full DomainKits policy for all 38 tools.
These attack patterns abuse exactly the kind of access tld_trends gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
gTLD registration trends over time. Analyze historical registration patterns for specific gTLDs — spot hype cycles, compare competing extensions, or check long-term health. Two modes: - action='data' + tld (single TLD): deep-dive into one TLD's trend over time. Use this to answer 'is .ai still hot?' or 'is .net dying?'. - action='compare' + tlds (comma-separated, max 5): side-by-side comparison. Use this to answer 'should I buy the .io or .ai version?' by comparing registration momentum. Best practices: - Focus on ma7 (7-day moving average) slope rather than raw daily numbers — daily counts are noisy, the moving average reveals the real trend direction. ma7 trending up = genuine momentum, flat = stable, declining = cooling off. - Compare ma7 vs ma14 for trend acceleration: ma7 crossing above ma14 = momentum building, ma7 dropping below ma14 = momentum fading. - type='newly' shows registration velocity (new domains per day) — best for detecting hype cycles and short-term momentum shifts. - type='active' shows total installed base — best for market size comparison and long-term health assessment. - When comparing TLDs, note the absolute scale difference — a TLD with 100K active domains showing 500 new/day has very different dynamics than one with 10M active showing 500 new/day. - Mutually exclusive inputs: action='data' requires 'tld' (single). action='compare' requires 'tlds' (comma-separated). Do not mix them. - days must be one of the allowed values: 7, 14, 30, 60, 90, 180. Use 30 for short-term momentum, 90-180 for trend confirmation. - Pairs well with tld_rank for today's snapshot context, and price to check registration costs for trending TLDs.. It is categorised as a Execute tool in the DomainKits MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DomainKits MCP server in PolicyLayer and add a rule for tld_trends: 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_trends is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tld_trends 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_trends. 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_trends 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.