Perform reverse DNS lookup on IP address
AI agents call reverse_dns to retrieve information from MCP Recon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Reverse DNS lookup is a passive reconnaissance technique that queries public DNS records to resolve IP addresses to hostnames. It retrieves existing information with no capability to modify, delete, or execute code. The blast radius of misuse is minimal—an attacker could map IP addresses to hostnames but cannot damage systems or data through this read-only operation alone.
From the tool's definition Tool performs 'reverse DNS lookup on IP address' — a query operation that retrieves DNS information without modifying data or triggering side effects.
Documented attack patterns abuse exactly the kind of access reverse_dns gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Recon, and nothing reaches the server without passing your rules. This is the rule we recommend for reverse_dns:
{
"version": "1",
"default": "deny",
"tools": {
"reverse_dns": {}
}
}reverse_dns is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Perform reverse DNS lookup on IP address. It is categorised as a Read tool in the MCP Recon MCP Server, which means it retrieves data without modifying state.
Register the MCP Recon 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 MCP Recon. 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 MCP Recon MCP server (sundayz-hunter/mcp_recon). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Recon, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 MCP Recon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.