dns_lookup
Look up DNS records and SSL information for any domain. Use this to check A, AAAA, MX, NS, TXT, and CNAME records, plus SSL certificate status and server info. Ideal for domain research, troubleshooting, and infrastructure verification. Parameters: domain — The domain name to query (e.g. "example...
This record as markdown: /tools/com-gadgethumans-swarm-x402-middleware/dns-lookup.md
What dns_lookup does on X402 Middleware
AI agents call dns_lookup to retrieve information from X402 Middleware 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 dns_lookup is rated Low
DNS lookups and SSL certificate verification are passive reconnaissance activities that query existing records. No data is created, modified, deleted, or executed. The tool enables information gathering about domain infrastructure but produces no side effects on the queried systems or data.
From the tool's definition Tool performs DNS lookups and retrieves SSL certificate information. The description explicitly states it checks 'A, AAAA, MX, NS, TXT, and CNAME records, plus SSL certificate status and server info' — all read-only operations that retrieve data without…
Attacks that exploit this kind of access
The rule that runs dns_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and X402 Middleware, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dns_lookup, this is the rule to start with:
dns_lookup 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 X402 Middleware, apply this rule, and every dns_lookup call is checked against it from then on.
Questions about dns_lookup
Look up DNS records and SSL information for any domain. Use this to check A, AAAA, MX, NS, TXT, and CNAME records, plus SSL certificate status and server info. Ideal for domain research, troubleshooting, and infrastructure verification. Parameters: domain — The domain name to query (e.g. "example.com"). It is categorised as a Read tool in the X402 Middleware MCP Server, which means it retrieves data without modifying state.
dns_lookup accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the X402 Middleware MCP server in PolicyLayer and add a rule for dns_lookup: 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 X402 Middleware. Nothing to install.
dns_lookup 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 dns_lookup 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 dns_lookup. 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.
dns_lookup is provided by the X402 Middleware MCP server (@gadgethumans/x402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on X402 Middleware, and thousands of servers like it.
This server
Across the catalogue