dns-mcp.blackveilsecurity.com

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

This server isn't on gate's handpicked list. That's not necessarily bad, but there's no third-party signal about it — review its tools carefully.

This tool accepts a caller-supplied webhook_url and will periodically POST brand-audit diff data (classification drift) to it on a recurring schedule. While SSRF revalidation is noted, an arbitrary external endpoint that receives ongoing scan/audit data about a domain constitutes a potential data-exfiltration channel if the webhook URL is attacker-supplied or later hijacked. Agents should confirm the webhook destination is trusted/expected by the user before registering a watch.

When verify_cap=true, the tool fetches capability documents from URLs declared in DNS TXT/SVCB records (cap=) rather than user-supplied URLs. Since DNS content could be attacker-influenced on domains not fully controlled by the requester, this creates a limited SSRF-like fetch surface. It is disabled by default and uses safeFetch, which mitigates but does not eliminate the concern; flagged for awareness only.