This record as markdown: /tools/com-geekflare-mcp/dnsrecord.md
What dnsRecord does on Mcp
AI agents call dnsRecord to retrieve information from Mcp 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 |
|---|---|---|---|
url | string | Yes | Target URL |
types | array | — |
Parameters from the server's own tool schema.
Why dnsRecord is rated Low
The tool queries and returns DNS information about a domain. This has no side effects, does not modify data, and does not execute commands or trigger external operations. It is purely informational retrieval. The blast radius of misuse is low: an attacker might enumerate DNS records for reconnaissance, but this is non-destructive and does not grant write, execute, or financial capabilities.
From the tool's definition 'Retrieve DNS records for a domain' — the verb 'retrieve' indicates a query operation that fetches data without modifying it. DNS record lookup is a standard read-only network diagnostic operation.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs dnsRecord safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dnsRecord, this is the rule to start with:
dnsRecord 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 Mcp, apply this rule, and every dnsRecord call is checked against it from then on.
Questions about dnsRecord
Retrieve DNS records for a domain. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
dnsRecord accepts 2 parameters: url, types. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for dnsRecord: 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 Mcp. Nothing to install.
dnsRecord 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 dnsRecord 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 dnsRecord. 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.
dnsRecord is provided by the MCP server (@geekflare/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue