# domain_check_batch_v1

Runs the full resilience check on up to 100 domains in a single call and returns the same scored report for each one: TLS certificate, security headers, DNS redundancy, response time, with every individual finding. Use it to audit a portfolio, to rank a list of vendors, or to re-check a fleet after a config rollout. One payment covers the whole batch instead of one per domain, which is why it is both cheaper per domain and much faster than calling domain_check_v1 in a loop. A domain that cannot be reached is returned with its own error rather than failing the batch, and it is still charged, because the crawl was attempted. Do not use it for a single domain: domain_check_v1 is simpler and costs the same for one. Private, internal and localhost hostnames and IP addresses are rejected. Price: $0.01 per domain, dropping to $0.005 from 100 domains, up to 100 per call. One payment covers the whole batch (x402, USDC on Base). No signup, no API key.

Agent View of the PolicyLayer registry record for `domain_check_batch_v1`. HTML page: https://policylayer.com/tools/com-feranor-resilience/domain-check-batch-v1

## Facts

- Tool: `domain_check_batch_v1`
- Server: Feranor Resilience (`https://www.feranor.com/mcp`) — https://policylayer.com/tools/com-feranor-resilience.md
- Homepage: https://github.com/https://www.feranor.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `domains` | array | yes | Bare domain names, apex or subdomain, for example ['example.com', 'www.example.org']. Between 1 and 100 entries. Scheme, path, port and query string are ignored |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "domain_check_batch_v1",
    "arguments": {
      "domains": []
    }
  }
}
```

## Why domain_check_batch_v1 is rated Low

This tool queries external domains and retrieves their security/resilience metrics without modifying any data or executing arbitrary code. It is purely informational assessment. The only side effect is a financial charge ($0.01/call), but the tool itself does not move money or commit obligations—it simply triggers a billable service call.

From the tool's own definition: "Tool performs 'Runs the full resilience check' and 'returns the same scored report' on domains. It gathers and returns information about TLS certificates, security headers, DNS redundancy, and response times."

## Use case

AI agents call domain_check_batch_v1 to retrieve information from Feranor Resilience without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Feranor Resilience:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "domain_check_batch_v1": {}
  }
}
```

## Other tools on Feranor Resilience (2)

- `domain_check_score_v1` — Read — https://policylayer.com/tools/com-feranor-resilience/domain-check-score-v1.md
- `domain_check_v1` — Read — https://policylayer.com/tools/com-feranor-resilience/domain-check-v1.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-feranor-resilience · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-feranor-resilience