Deep keyword intelligence for domain investment. Call when a user wants to understand the full picture of a specific keyword in the domain market — demand, supply, competition, and opportunities. This is a data-intensive workflow: every claim must be backed by tool output. When to use: User asks ...
Part of the DomainKits server.
Free to start. No card required.
AI agents may call keyword_intel to permanently remove or destroy resources in DomainKits. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call keyword_intel in a loop, permanently destroying resources in DomainKits. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"keyword_intel"
]
}See the full DomainKits policy for all 38 tools.
These attack patterns abuse exactly the kind of access keyword_intel gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Deep keyword intelligence for domain investment. Call when a user wants to understand the full picture of a specific keyword in the domain market — demand, supply, competition, and opportunities. This is a data-intensive workflow: every claim must be backed by tool output. When to use: User asks about a keyword's investment potential, market landscape, or opportunity analysis. Not for analyzing a specific domain (use analyze), browsing trends (use trend_hunter), or market overviews (use market_beat). Methodology — three phases, each building on the previous: 1. Demand: Establish how much the market wants this keyword. - keyword_data for commercial search value (volume, CPC, competition). - keywords_trends (both hot and emerging) for registration momentum. - web_search is MANDATORY — do NOT substitute with your own knowledge. Execute at least two searches: '{keyword} news 2026' for industry context, and '{keyword} domain sold price' for transaction history. Only include claims that come from search results. If search returns nothing relevant, state 'no recent news or transactions found' — do not fill the gap with training data. Do NOT attribute keyword popularity to a specific event or project unless keywords_trends data shows a clear spike AND web_search confirms the connection. Common English words have natural baseline demand — not every trend needs a catalyst explanation. 2. Supply: Map the current domain inventory, focused on .com as the primary lens unless the user requests otherwise. - tld_check for cross-TLD saturation. - active for total .com inventory and for-sale ratio (forsale count / total count). Also compare keyword-as-prefix vs keyword-as-suffix to gauge market maturity. - deleted for domains available at standard registration cost. - expired for domains in the expiration pipeline that can be backordered. - aged with has_sale=true for secondary market listings. 3. Competition: Assess whether the window is opening or closing. - nrds comparing recent .com registration velocity across time periods (0-10 days vs 10-20 days). Accelerating velocity means act fast; decelerating means the peak may have passed. - From the same nrds results, assess registration quality — high ratios of hyphens, numbers, or excessive length indicate a junk/speculative market rather than serious investment. - Analyze the naming patterns in recent registrations to identify what is driving demand. For example, if most new domains combine the keyword with 'ai', 'cloud', 'tech', that points to a tech trend; if they combine with 'game', 'machine', 'play', that points to entertainment. If patterns are diverse with no clear theme, the keyword likely has natural baseline demand across multiple sectors. This pattern analysis is based on the nrds results already retrieved — no additional tool calls needed. Synthesize into an intelligence report: keyword verdict (invest / watch / avoid) with confidence level, demand profile, supply profile, competition profile, and recommended next steps tailored to the verdict. Let the data tell the story — if data is contradictory, present both sides. After the report, offer relevant next steps: deep analysis on a specific domain, brand conflict check, monitoring setup, strategy tracking, or analyzing a different keyword.. It is categorised as a Destructive tool in the DomainKits MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DomainKits MCP server in PolicyLayer and add a rule for keyword_intel: 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.
keyword_intel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the keyword_intel 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 keyword_intel. 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.
keyword_intel 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.