reconng_run
AI agents invoke reconng_run to trigger actions in Kali Linux MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an external reconnaissance/OSINT framework (Recon-ng) whose effects depend entirely on which modules and targets the AI provides as arguments. It is not a simple read operation—it performs active reconnaissance that can trigger external requests, generate network traffic, and return sensitive information about targets.
From the tool's definition Tool name 'reconng_run' indicates execution of Recon-ng, a reconnaissance and OSINT framework. The server description explicitly mentions 'OSINT capabilities' and lists sibling tools like 'amass_scan' and 'arping_scan' that are scanning/discovery tools.
Attacks that exploit this kind of access
reconng_run. It is categorised as a Execute tool in the Kali Linux MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Linux MCP Server MCP server in PolicyLayer and add a rule for reconng_run: 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 Kali Linux MCP Server. Nothing to install.
reconng_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the reconng_run 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 reconng_run. 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.
reconng_run is provided by the Kali Linux MCP Server MCP server (ofryma/custom-mcp-library). 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 →