Manage domain monitoring tasks. Track changes in WHOIS, DNS, and page content. All monitoring data is encrypted at rest (AES-256-GCM) and stored in your private directory. GDPR compliant. Actions: - get: Retrieve and auto-check all monitors. Default action if not specified. Automatically performs...
Part of the DomainKits server.
Free to start. No card required.
AI agents call monitor 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 monitor 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": {
"monitor": {}
}
}See the full DomainKits policy for all 38 tools.
These attack patterns abuse exactly the kind of access monitor 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.
Manage domain monitoring tasks. Track changes in WHOIS, DNS, and page content. All monitoring data is encrypted at rest (AES-256-GCM) and stored in your private directory. GDPR compliant. Actions: - get: Retrieve and auto-check all monitors. Default action if not specified. Automatically performs bulk WHOIS and DNS checks where the minimum interval has passed. You do NOT need to manually call whois or dns tools. For each monitor where can_check=true, returns current vs previous data with change flags. For can_check=false monitors, returns last known data and next_check time. YOUR JOB: focus on whois_changed=true or dns_changed=true, report with context from note field. For DNS, focus on NS changes — ignore A/AAAA (CDN rotation). If monitors have web_fetch in tools, optionally run web_fetch yourself then call with action=update to save results. - set: Create a new monitor. Requires registered account and memory enabled. Max 100 monitors. Before creating, verify memory is enabled via preferences. WHOIS and DNS are auto-checked when you call action=get — no need to call them manually. web_fetch is optional and must be run manually. - update: Save web_fetch page results for a monitor. WHOIS and DNS are auto-saved by action=get — you only need this for web_fetch page content. Typical flow: call action=get (auto-checks WHOIS/DNS), run web_fetch yourself, then call action=update with the page summary. The whois and dns parameters are accepted for backward compatibility but normally not needed. - delete: Remove a monitor task. Requires registered account (member or above) and memory enabled for all actions.. 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 monitor: 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.
monitor 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 monitor 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 monitor. 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.
monitor 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.