Comprehensive domain analyze workflow. Call when a user wants to understand a specific domain's full picture — registration status, safety, DNS configuration, cross-TLD distribution, and current website usage. When to use: user asks 'what can you tell me about example.com?', wants to evaluate a d...
Part of the DomainKits server.
Free to start. No card required.
AI agents call analyze 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 analyze 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": {
"analyze": {}
}
}See the full DomainKits policy for all 38 tools.
These attack patterns abuse exactly the kind of access analyze 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.
Comprehensive domain analyze workflow. Call when a user wants to understand a specific domain's full picture — registration status, safety, DNS configuration, cross-TLD distribution, and current website usage. When to use: user asks 'what can you tell me about example.com?', wants to evaluate a domain before purchasing, or needs a technical analyze. Do NOT use for domain name ideas (use name_advisor), availability checks (use available), or expired domain evaluation (use expired_analysis). Workflow: 1. Gather data using all four atomic tools in parallel: - whois for registration details, registrar signals, and expiry dates. - safety for Google Safe Browsing status. - dns for MX, A, and CNAME records — signals of active usage or abandonment. - tld_check to see how many TLDs share this prefix. 2. If tld_check shows high registration count, investigate further: - whois the .com/.net/.org variants to check if the same registrar holds multiple TLDs (brand protection signal) or different registrars (popular keyword signal). - web_search the TLD variants to see if they resolve to the same site. 3. Visit the domain via web_fetch or web_search to determine current usage: active business, parked page, for-sale landing, or no content. 4. Use web_search to investigate the domain's market background: recent sale history (NameBio, Sedo, Afternic), related news or brand events, legal disputes (UDRP, trademark conflicts), and any notable context that affects valuation or risk. This step is critical — technical data alone is insufficient for a complete analyze. 5. Synthesize all findings into a concise analyze report. Present facts with key signals clearly flagged. Do NOT make buy/don't-buy judgments — present evidence and let the user decide. 6. After presenting the report, ask the user about their goals before suggesting next steps. Tailor follow-up based on their answer: - Wants to purchase → suggest valuation_cma for pricing, brand_match for trademark risk. - Domain is listed for sale → provide the sale link, suggest brand_match. Disclose affiliate links. - Wants alternatives → suggest plan_b. - Wants monitoring → suggest set_monitor. Key principles: present facts, not recommendations. Flag signals clearly (e.g., enterprise registrar = corporate-held, MX present = active email, no A record = possibly abandoned). Every claim must come from tool data. Disclose affiliate links when presenting registration or sale URLs.. 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 analyze: 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.
analyze 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 analyze 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 analyze. 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.
analyze 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.