Compare a target domain against a reference for phishing / typosquatting / lookalike detection. Computes edit distance, apex/TLD diff, homoglyph substitution detection (0↔o, 1↔l, rn↔m). Flags is_likely_typosquat + is_likely_lookalike with drivers. Pure analytical comparison — no DNS query.
Part of the Ready APIs server.
Free to start. No card required.
AI agents use dns_compare to create or modify resources in Ready APIs. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call dns_compare repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Ready APIs.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"dns_compare": {
"limits": [
{
"counter": "dns_compare_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} See the full Ready APIs policy for all 129 tools.
These attack patterns abuse exactly the kind of access dns_compare gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Compare a target domain against a reference for phishing / typosquatting / lookalike detection. Computes edit distance, apex/TLD diff, homoglyph substitution detection (0↔o, 1↔l, rn↔m). Flags is_likely_typosquat + is_likely_lookalike with drivers. Pure analytical comparison — no DNS query.. It is categorised as a Write tool in the Ready APIs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ready APIs MCP server in PolicyLayer and add a rule for dns_compare: 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 Ready APIs. Nothing to install.
dns_compare is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dns_compare 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 dns_compare. 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.
dns_compare is provided by the Ready APIs MCP server (https://readyapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 129 Ready APIs 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.