Full-featured reconnaissance framework with modules for OSINT gathering.
AI agents call recon_ng to retrieve information from MCP Kali Pentest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Recon_ng is a passive information gathering tool that collects publicly available intelligence about targets (IP addresses, domain names, employee information, etc.). While it has medium severity due to the sensitive nature of reconnaissance data and its role in preparing for attacks, it performs no Write, Execute, Destructive, or Financial operations. The risk is informational rather than operational.
From the tool's definition Tool is described as a 'reconnaissance framework with modules for OSINT gathering.' Reconnaissance and OSINT (Open Source Intelligence) gathering are data retrieval and analysis activities with no capability to modify, delete, or execute code on target…
Attacks that exploit this kind of access
Full-featured reconnaissance framework with modules for OSINT gathering. It is categorised as a Read tool in the MCP Kali Pentest MCP Server, which means it retrieves data without modifying state.
Register the MCP Kali Pentest MCP server in PolicyLayer and add a rule for recon_ng: 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 Kali Pentest. Nothing to install.
recon_ng 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 recon_ng 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 recon_ng. 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.
recon_ng is provided by the MCP Kali Pentest MCP server (root1856/mcpkali). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →