run_dig_lookup · External Reconnaissance MCP Server MCP

WHAT IT DOES

What run_dig_lookup does on External Reconnaissance MCP Server

AI agents call run_dig_lookup to retrieve information from External Reconnaissance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why run_dig_lookup needs a policy

This tool performs a DNS A record lookup, which is a passive read/query operation with no side effects. However, the server context is explicitly for 'external reconnaissance activities,' which elevates severity since misuse could support targeted attacks. The tool itself only retrieves DNS data, placing it in the Read category, but the reconnaissance context warrants a medium severity rating.

From the tool's definition perform simple lookup of any A records for the domain

Documented attack patterns abuse exactly the kind of access run_dig_lookup gives an agent:

POLICY

How to control run_dig_lookup

PolicyLayer is an MCP gateway — it sits between your AI agents and External Reconnaissance MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_dig_lookup:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_dig_lookup": {}
  }
}

run_dig_lookup is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register External Reconnaissance MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More External Reconnaissance MCP Server tools

Execute bruteforce_subdomains Bruteforce subdomains using dnsrecon and custom wordlist. Execute enumerate_subdomains Enumerate subdomains using dnsrecon tool. Execute attempt_zone_transfer Attempt to perform a DNS zone transfer (AXFR) to enumerate all DNS records. Read enumerate_dns_records Enumerate various DNS record types for the target domain. Read run_whois_lookup perform query of domain ownership details. Read analyze_http_headers Analyze HTTP headers of the target domain. Read check_email_security Check email security configuration

All 8 External Reconnaissance MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about run_dig_lookup

What does the run_dig_lookup tool do? +

perform simple lookup of any A records for the domain. It is categorised as a Read tool in the External Reconnaissance MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on run_dig_lookup? +

Register the External Reconnaissance MCP Server MCP server in PolicyLayer and add a rule for run_dig_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 External Reconnaissance MCP Server. Nothing to install.

What risk level is run_dig_lookup? +

run_dig_lookup is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit run_dig_lookup? +

Yes. Add a rate_limit block to the run_dig_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.

How do I block run_dig_lookup completely? +

Set action: deny in the PolicyLayer policy for run_dig_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.

What MCP server provides run_dig_lookup? +

run_dig_lookup is provided by the External Reconnaissance MCP Server MCP server (naebo/mcp-external-recon-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every External Reconnaissance MCP Server tool call.

Start from External Reconnaissance MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

8 External Reconnaissance MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.