BlackVeil DNS & Email Security Scanner

check_zone_hygiene

Read-onlyIdempotent

Audit DNS zone hygiene: identifies sensitive or forgotten subdomains exposed in DNS, stale SOA records, and zone propagation issues. Use to find any sensitive subdomains that should not be publicly visible, or to audit overall DNS zone cleanliness.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "check_zone_hygiene"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes	Domain, e.g. example.com
`format`	No	Output verbosity.
`force_refresh`	No	Bypass the cache.

Output Schema

Name	Required	Description	Default
`score`	Yes
`passed`	Yes
`partial`	No
`category`	Yes
`findings`	Yes
`checkStatus`	No
`verdictWithheld`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 12, 2026

changedInput schema / properties / domain / description

Previous value: -"Domain to check (e.g., example.com)"New value: +"Domain, e.g. example.com"

changedInput schema / properties / force_refresh / description

Previous value: -"Bypass cache and run a fresh check. Useful after DNS changes."New value: +"Bypass the cache."

changedInput schema / properties / format / description

Previous value: -"Output verbosity. Auto-detected if omitted."New value: +"Output verbosity."

Changed1 schema field changedOct 25, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Changed1 schema field changedOct 5, 2026
- addedOutput schema / properties / verdictWithheld
```
Added value: +{
+  "type": "boolean"
+}
```
Changed2 schema fields changedAug 18, 2026
- addedOutput schema / properties / checkStatus
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```

Changed1 schema field changedJul 2, 2026

addedInput schema / properties / force_refresh

Added value: +{
+  "description": "Bypass cache and run a fresh check. Useful after DNS changes.",
+  "type": "boolean"
+}

Changed1 schema field changedMay 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "category": {
+      "type": "string"
+    },
+    "findings": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "passed": {
+      "type": "boolean"
+    },
+    "score": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "category",
+    "score",
+    "passed",
+    "findings"
+  ],
+  "type": "object"
+}

First observedApr 21, 2026

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without the description. The description adds the categories of issues the audit reports, which is useful behavioral context, but says nothing about how many queries it makes, whether results are cached (relevant given the force_refresh parameter), or any rate/latency considerations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the audit scope front-loaded; efficient overall. The second sentence largely paraphrases the first, so a small amount of wording does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With rich annotations and an output schema, the description needn't explain returns or safety, and it does convey the audit's subject matter. What is missing is positional clarity: an agent choosing among shadow-domain, resolver-consistency, NS and DNSSEC checks has no basis from the description for picking this one.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including the domain example and the format enum, so the schema already carries parameter meaning. The description contributes nothing about 'domain' scope (apex vs subdomain), 'format' verbosity, or when 'force_refresh' matters, leaving it at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ('Audit') with a specific resource ('DNS zone hygiene') and enumerates the concrete findings it surfaces: sensitive/forgotten subdomains, stale SOA records, and propagation issues. It does not, however, differentiate itself from near-neighbors in the catalog such as check_shadow_domains or check_resolver_consistency, which appear to overlap on subdomain exposure and propagation respectively.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence ('Use to find any sensitive subdomains... or to audit overall DNS zone cleanliness') restates the purpose rather than giving real routing guidance. There are no when-not-to-use conditions and no named alternatives, so an agent facing the crowded check_* sibling set must infer which tool applies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BlackVeil DNS & Email Security Scanner tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.