Domain buyer discovery workflow. Call when a user wants to find potential end-user buyers for a domain they own or are considering selling. When to use: user asks 'who would buy this domain?', 'help me sell [domain]', or wants to find buyers as a follow-up after keyword_intel or plan_b. Do NOT us...
Risk signalsBulk/mass operation — affects multiple targets
Part of the DomainKits server.
Free to start. No card required.
AI agents invoke sale_chance 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.
sale_chance 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": {
"sale_chance": {
"limits": [
{
"counter": "sale_chance_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 sale_chance 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.
Domain buyer discovery workflow. Call when a user wants to find potential end-user buyers for a domain they own or are considering selling. When to use: user asks 'who would buy this domain?', 'help me sell [domain]', or wants to find buyers as a follow-up after keyword_intel or plan_b. Do NOT use when the user wants to buy a domain (use plan_b), check domain value only (use valuation_cma), or analyze a domain technically (use analyze). Workflow: 1. Extract the core keyword(s) from the domain. Use web_search '[keyword] company OR brand OR product' to discover who is already operating under this name or close variants. Note their business type, current domain, scale, and how long they've been using the keyword. This research step is mandatory — do not skip it. 2. Categorize potential buyers into three tiers by purchase motivation: - Tier 1 — Domain Upgraders: companies already operating under this exact name or a close variant (on .net, .io, a hyphenated version, or with a prefix/suffix added), who would naturally want the cleaner or shorter version. These are the highest-intent buyers — they've already built equity around the keyword and this domain is a direct upgrade for them. - Tier 2 — Strategic Expansioners: companies in the same industry whose product, feature, or campaign aligns with what this domain describes. Acquiring it is a strategic fit that strengthens positioning. - Tier 3 — New Brand Builders: funded startups or new ventures that haven't fully launched yet but would find this name ideal. 3. Use Claude for Chrome to research buyers on LinkedIn in three layers. Open LinkedIn in the browser and execute the following searches in order: Layer 1 — Find Domain Upgraders (highest priority): Switch to the Companies tab. Search using the exact keyword and close variants: "[keyword]" OR "[keywords]" OR "[keyword]-[common suffix]" Scan results for companies whose name or description contains the keyword but whose website is on an inferior domain (not the clean .com). These are Tier 1 buyers. Layer 2 — Find Strategic Buyers: Search Companies tab by industry theme: "[industry vertical] [keyword theme]" Apply Industry filter (e.g., Events Services, Software, Media) to narrow results. Identify Tier 2 candidates whose business would be strengthened by owning this domain. Layer 3 — Find Decision Makers at identified companies: For each promising company from Layers 1 and 2, switch to the People tab and use Boolean search to locate the right contact: ("CMO" OR "VP Marketing" OR "Chief Marketing" OR "Brand Director" OR "Head of Brand" OR "Head of Marketing") AND "[company name]" NOT (intern OR assistant) Record: full name, title, LinkedIn profile URL. 4. Synthesize findings into a prioritized buyer list. Present Tier 1 first, then Tier 2, then Tier 3. For each entry include: company name, current domain they operate on, reason they are a strong buyer candidate, and decision maker contact if found. 5. After presenting the buyer list, ask the user what they want to do next. Tailor follow-up based on their response: - Wants a price before outreach → suggest valuation_cma for a data-backed asking price, market_price to check existing listings. - Wants to draft outreach → help write a personalized email for each Tier 1 buyer, emphasizing the specific upgrade value to their existing brand. - Wants to list the domain → suggest Afternic, Sedo, or Dan.com depending on domain type. - Wants more buyer leads → suggest brand_match to identify additional companies using the keyword, or nrds to see who has recently registered variants. Key principles: focus on upgrade motivation, not conflict framing. Every buyer candidate must be grounded in data from web_search or LinkedIn results. Do not speculate about intent. Present the buyer list as opportunity intelligence, not legal risk assessment. Disclose affiliate links when presenting marketplace URLs.. 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 sale_chance: 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.
sale_chance 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 sale_chance 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 sale_chance. 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.
sale_chance 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.