Check domain safety via Google Safe Browsing, and check Google search index status. Returns two pieces of data: (1) safe — whether Google Safe Browsing flags the domain for malware, phishing, social engineering, or unwanted software, including specific threat types if flagged; (2) index — whether...
Part of the DomainKits server.
Free to start. No card required.
AI agents call safety 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 safety 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": {
"safety": {}
}
}See the full DomainKits policy for all 38 tools.
These attack patterns abuse exactly the kind of access safety 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.
Check domain safety via Google Safe Browsing, and check Google search index status. Returns two pieces of data: (1) safe — whether Google Safe Browsing flags the domain for malware, phishing, social engineering, or unwanted software, including specific threat types if flagged; (2) index — whether the domain has pages indexed in Google and an estimated count. A flagged domain is a critical risk signal — it likely has a problematic history (malware distribution, phishing, spam operations) that may be difficult or impossible to recover from. This is especially important when evaluating expired or aged domains for acquisition. An unindexed domain may indicate it was previously penalized or has been dormant.. 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 safety: 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.
safety 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 safety 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 safety. 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.
safety 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.