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 aft...
This record as markdown: /tools/com-feranor-resilience/domain-check-batch-v1.md
What domain_check_batch_v1 does on Feranor Resilience
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.
| 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.
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 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.
Attacks that exploit this kind of access
The rule that runs domain_check_batch_v1 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Feranor Resilience, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domain_check_batch_v1, this is the rule to start with:
domain_check_batch_v1 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Feranor Resilience, apply this rule, and every domain_check_batch_v1 call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Feranor Resilience MCP Server, which means it retrieves data without modifying state.
domain_check_batch_v1 accepts 1 parameter: domains. Required: domains. The full parameter table on this page comes from the server's own tool schema.
Register the Feranor Resilience MCP server in PolicyLayer and add a rule for domain_check_batch_v1: 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 Feranor Resilience. Nothing to install.
domain_check_batch_v1 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 domain_check_batch_v1 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 domain_check_batch_v1. 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.
domain_check_batch_v1 is provided by the Feranor Resilience MCP server (https://www.feranor.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Feranor Resilience, and thousands of servers like it.
This server
Across the catalogue