// SCAN REPORT

MCP Recon

13 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

2 can modify or destroy data

11 read-only

13 tools total

Community server · catalogue entry verified 12/06/2026

How to control MCP Recon ↓

TOOL MAP

What MCP Recon exposes to your agents

Read (11) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous MCP Recon tools

Execute · High port_scan This tool executes nmap, an external network scanning program, against target hosts. Execute · Medium subdomain_enum_active This tool performs active DNS brute-force enumeration, meaning it sends network requests to external targets to discover subdomains.

2 of MCP Recon's 13 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MCP Recon

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Recon, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "check_alive": {
    "limits": [
      {
        "counter": "check_alive_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register MCP Recon — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP RECON →

Free to start. No card required.

FULL CATALOGUE

All 13 MCP Recon tools

EXECUTE 2 tools

Execute port_scan Advanced port scan using nmap Execute subdomain_enum_active Enumerate subdomains using DNS brute force (active reconnaissance)

READ 11 tools

Read check_alive check_alive Read detect_technologies detect_technologies Read dns_records Perform comprehensive DNS lookups for all record types Read domain_history Check domain history and reputation indicators Read extract_urls extract_urls Read http_headers http_headers Read ip_information Get comprehensive IP information including geolocation Read reverse_dns Perform reverse DNS lookup on IP address Read subdomain_enum_passive Passive subdomain enumeration using Certificate Transparency logs Read tls_certificate Check TLS certificate details and security using Python SSL Read whois_info Get comprehensive WHOIS information for a domain

FAQ

Questions about MCP Recon

Is the MCP Recon MCP server safe to use without restrictions? +

The MCP Recon server is primarily read-only with 11 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the MCP Recon MCP server expose? +

13 tools across 1 categories: Read. 11 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on MCP Recon? +

Register the MCP Recon MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every MCP Recon tool call.

Deterministic rules across all 13 MCP Recon tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP RECON →

Free to start. No card required.

13 MCP Recon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.