dnssec_check
DNSSEC status of a domain over DNS-over-HTTPS: secure / insecure / bogus (validation failure) / island (signed but no DS at the parent), the zone apex, DS records (key tag, algorithm, digest type) and DNSKEYs (KSK / ZSK, algorithm, computed key tag), whether each DS digest really matches a publis...
This record as markdown: /tools/com-it-scorptech-x402/dnssec-check.md
What dnssec_check does on ScorpTech x402 API
AI agents call dnssec_check to retrieve information from ScorpTech x402 API 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 |
|---|---|---|---|
domain | string | Yes |
Parameters from the server's own tool schema.
Why dnssec_check is rated Low
Even though dnssec_check only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs dnssec_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dnssec_check, this is the rule to start with:
dnssec_check 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 ScorpTech x402 API, apply this rule, and every dnssec_check call is checked against it from then on.
Questions about dnssec_check
DNSSEC status of a domain over DNS-over-HTTPS: secure / insecure / bogus (validation failure) / island (signed but no DS at the parent), the zone apex, DS records (key tag, algorithm, digest type) and DNSKEYs (KSK / ZSK, algorithm, computed key tag), whether each DS digest really matches a published DNSKEY (recomputed locally), and warnings for deprecated algorithms or SHA-1 digests (RFC 8624). Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/dnssec-check. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
dnssec_check accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for dnssec_check: 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 ScorpTech x402 API. Nothing to install.
dnssec_check 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 dnssec_check 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 dnssec_check. 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.
dnssec_check is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue