exploit_suggest_from_nmap
Analyze nmap scan output and suggest exploits for discovered services.
This record as markdown: /tools/zebbern-zebbern-kali-mcp/exploit-suggest-from-nmap.md
What exploit_suggest_from_nmap does on Zebbern Kali MCP
AI agents invoke exploit_suggest_from_nmap to trigger actions in Zebbern Kali MCP. 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.
Why exploit_suggest_from_nmap is rated High
This tool analyzes scan results and suggests exploits, which is an active step in a penetration testing attack chain. While 'suggesting' exploits is nominally read-like, in context of a Kali Linux toolkit with sibling tools like ad_psexec, ad_secretsdump, and ad_password_spray, this tool facilitates exploitation of live systems.
From the tool's definition 'Analyze nmap scan output and suggest exploits for discovered services' — actively maps discovered services to known exploits, functioning as an offensive reconnaissance-to-exploitation bridge
Attacks that exploit this kind of access
The rule that runs exploit_suggest_from_nmap safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zebbern Kali MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For exploit_suggest_from_nmap, this is the rule to start with:
exploit_suggest_from_nmap stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Zebbern Kali MCP, apply this rule, and every exploit_suggest_from_nmap call is checked against it from then on.
Questions about exploit_suggest_from_nmap
Analyze nmap scan output and suggest exploits for discovered services. It is categorised as a Execute tool in the Zebbern Kali MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Zebbern Kali MCP server in PolicyLayer and add a rule for exploit_suggest_from_nmap: 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 Zebbern Kali MCP. Nothing to install.
exploit_suggest_from_nmap 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 exploit_suggest_from_nmap 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 exploit_suggest_from_nmap. 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.
exploit_suggest_from_nmap is provided by the Zebbern Kali MCP server (zebbern/zebbern-kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zebbern Kali, and thousands of servers like it.
Across the catalogue