reverse_dns
Reverse DNS (PTR) for up to 20 IPv4 / IPv6 addresses with forward-confirmed reverse DNS (FCrDNS: does the PTR hostname resolve back to the same IP?), PTR name, TTL and NXDOMAIN / SERVFAIL status, over DNS-over-HTTPS. Useful for mail-server checks, log enrichment and bot verification (e.g. is this...
This record as markdown: /tools/com-it-scorptech-x402/reverse-dns.md
What reverse_dns does on ScorpTech x402 API
AI agents call reverse_dns 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 |
|---|---|---|---|
ips | array | Yes | IPv4 / IPv6 addresses |
forward | boolean | — | Forward-confirm each PTR hostname |
Parameters from the server's own tool schema.
Why reverse_dns is rated Low
Even though reverse_dns 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 reverse_dns 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 reverse_dns, this is the rule to start with:
reverse_dns 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 reverse_dns call is checked against it from then on.
Questions about reverse_dns
Reverse DNS (PTR) for up to 20 IPv4 / IPv6 addresses with forward-confirmed reverse DNS (FCrDNS: does the PTR hostname resolve back to the same IP?), PTR name, TTL and NXDOMAIN / SERVFAIL status, over DNS-over-HTTPS. Useful for mail-server checks, log enrichment and bot verification (e.g. is this really Googlebot). Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/reverse-dns. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
reverse_dns accepts 2 parameters: ips, forward. Required: ips. 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 reverse_dns: 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.
reverse_dns 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 reverse_dns 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 reverse_dns. 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.
reverse_dns 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