Get trending keywords in domain registrations. Mainly used for investors to find new opportunities, but also useful for brand protection. Three modes: - hot: High-volume keywords (e.g., 'app', 'shop', 'group'). Established terms with high volume and high competition. Results include weekly breakd...
Part of the DomainKits server.
Free to start. No card required.
AI agents invoke keywords_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.
keywords_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": {
"keywords_trends": {
"limits": [
{
"counter": "keywords_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 keywords_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.
Get trending keywords in domain registrations. Mainly used for investors to find new opportunities, but also useful for brand protection. Three modes: - hot: High-volume keywords (e.g., 'app', 'shop', 'group'). Established terms with high volume and high competition. Results include weekly breakdown (w1-w4) to spot momentum shifts. Quality metrics use 28-day data. - emerging: Keywords with sudden registration spikes in the last 7-14 days, often driven by technology news, product launches, or viral projects. Compare w4 (current week) vs w3 to assess momentum. Quality metrics use W4-only data to reflect the spike period accurately. - prefix: Popular naming patterns (e.g., 'get...', 'my...', 'the...'). Results include tld_count — if a prefix has high tld_count but .com is still available, that is actionable. Use bulk_tld to check which specific TLDs are taken vs available. Quality metrics (hot and emerging only, fields vary by user tier): - com_ratio: .com registrations as a proportion of total. .com is the most expensive and most liquid TLD — this ratio reflects participants' willingness to invest real money. - most_tld: The dominant TLD for this keyword. Shows where registration activity is concentrated. - pos_start_ratio / pos_end_ratio: Where the keyword appears in domain names. High start ratio (e.g., 'aitools.com') suggests the keyword drives the domain concept. High end ratio (e.g., 'myai.com') suggests it is used as a modifier. - forsale_pct: Percentage of domains with NS pointing to sale platforms (Sedo, Afternic, Atom). Reflects investor participation — cross-reference with com_ratio and top_registrar to assess multi-party market participation. - top_ns + top_ns_ratio: The most common nameserver and its share. High concentration on a single NS indicates concentrated activity. Cross-reference with NS identity to understand what participants are doing with their domains. - top_registrar: The registrar with the highest volume. Registrars are channels, not identity labels — high concentration reduces confidence that many independent parties are involved, but does not by itself prove single-operator activity. Must be cross-referenced with other dimensions. - peak_day: The single day with highest registrations. If peak_day accounts for a large share of total, the trend may be event-driven or a single bulk registration event rather than sustained interest. - might_use_count: Domains with NS pointing to infrastructure providers (Cloudflare, AWS, Vercel, Netlify). Does NOT reliably indicate active sites — especially Cloudflare and AWS are widely used for DNS hosting, CDN, or parking. Must cross-reference with registrar diversity — high might_use_count with diverse registrars suggests organic adoption; high might_use_count with one dominant registrar suggests a single operator. Data methodology: Registration counts are based on semantic keyword extraction using DomainKits' proprietary word segmentation engine (https://github.com/ABTdomain/dksplit), not simple substring matching. Bulk registration noise is automatically filtered from emerging results. WHOIS data is sourced from daily RDAP snapshots. Brand protection registrars (CSC, MarkMonitor, etc.) are excluded.. 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 keywords_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.
keywords_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 keywords_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 keywords_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.
keywords_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.