Monitor changes to premium .com domains in the past 7 days. The monitored pool consists of short-character .com domains (typically 1-4 letters) and high-value English single-word and two-word .com domains. This is not a general domain monitor — it specifically tracks the most valuable segment of ...
Part of the DomainKits server.
Free to start. No card required.
AI agents call domain_changes 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 domain_changes 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": {
"domain_changes": {}
}
}See the full DomainKits policy for all 38 tools.
These attack patterns abuse exactly the kind of access domain_changes 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.
Monitor changes to premium .com domains in the past 7 days. The monitored pool consists of short-character .com domains (typically 1-4 letters) and high-value English single-word and two-word .com domains. This is not a general domain monitor — it specifically tracks the most valuable segment of the .com namespace. Change types: - Domain Transfer: Registrar changed — indicates ownership or management change. Report the old and new registrar as facts. Do not assume the reason (could be a sale, corporate restructuring, registrar migration, or portfolio consolidation). - Domain Expired: Domain entered expiration cycle. Report the fact. Do not characterize rarity or value unless verified with additional data. - New Registration: A previously unregistered premium name was registered. - Nameserver Change: NS records updated. An NS change to a domain marketplace (e.g., sedo.com, afternic.com, thisdomain.forsale) is a possible sale signal but not a certainty — report the old and new NS as facts. Best practices: - date_range=1d for last 24 hours, 3d for last 72 hours, all for full 7-day window (default). - length=1-3 or length=4 focuses on the shortest, most premium domains. - reason filters to a specific change type — use 'Domain Transfer' or 'Domain Expired' for the most newsworthy events. - sort=length_asc surfaces the shortest (most valuable) domains first. - has_digit=false filters to letter-only domains for higher quality results. - All interpretations must be evidence-based. Report what changed, not why. If the user wants to understand the reason behind a change, suggest whois or web_search to investigate further.. 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 domain_changes: 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.
domain_changes 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 domain_changes 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 domain_changes. 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.
domain_changes 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.