Search active gTLD domains from a database of ~240 million registered domains. This tool is primarily a market analysis instrument — use it to understand keyword distribution, saturation, and market dynamics through comparative queries. Core analysis dimensions (typically requiring multiple calls...
Risk signalsHigh parameter count (10 properties)
Part of the DomainKits server.
Free to start. No card required.
AI agents invoke active 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.
active 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": {
"active": {
"limits": [
{
"counter": "active_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 active 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.
Search active gTLD domains from a database of ~240 million registered domains. This tool is primarily a market analysis instrument — use it to understand keyword distribution, saturation, and market dynamics through comparative queries. Core analysis dimensions (typically requiring multiple calls per keyword): - TLD distribution: Compare total_found with no tld filter vs tld=com vs tld=net vs others to calculate .com concentration and cross-TLD spread. - Position distribution: Compare position=start vs position=end to gauge market maturity. Start-heavy means the keyword is used as a category anchor (e.g., 'aiwriter.com'); end-heavy means it has become a standard descriptor (e.g., 'writerai.com'). - For-sale ratio: Compare status=forsale total_found vs unfiltered total_found. High ratio (>30%) suggests speculator saturation; low ratio (<10%) suggests most holders are actively using their domains. - Quality distribution: Compare type=all_alpha total_found vs unfiltered total. If the majority of registrations contain hyphens or numbers, the keyword is dominated by low-quality or spam registrations — a negative signal. - Length distribution: Compare total_found across length filters (<5, 5-10, 11-15, >15) to assess how much premium short-name inventory exists vs long-tail. Best practices: - keyword defaults to 'contain' matching (substring). This is appropriate for statistical analysis but produces large result sets. Use position=start or position=end when analyzing directional distribution. - The total_found field across multiple filtered calls is the primary analytical output — the actual domain list is secondary. - sort=length_asc surfaces the shortest (most premium) names first when browsing results. - status=forsale filters to domains explicitly listed for sale — these are acquisition targets. - no_hyphen and no_number are independent boolean parameters, separate from the type filter. - Disclose affiliate links when presenting register_url to users.. 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 active: 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.
active 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 active 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 active. 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.
active 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.