AI agents call fetch_nmap_results to retrieve information from pentestMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves previously-collected Nmap scan results, which is a read operation. However, given the pentestMCP server's purpose (penetration testing) and the nature of Nmap data (network reconnaissance details like open ports, services, vulnerabilities), the severity is elevated to medium because disclosure of this information to an unauthorized or compromised AI agent could facilitate attacks on the scanned…
From the tool's definition Tool name uses 'fetch' and description states 'Non-blocking fetch for Nmap scan results' — retrieves data without modifying or deleting it.
Documented attack patterns abuse exactly the kind of access fetch_nmap_results gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and pentestMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_nmap_results:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_nmap_results": {}
}
}fetch_nmap_results is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Non-blocking fetch for Nmap scan results:. It is categorised as a Read tool in the pentestMCP MCP Server, which means it retrieves data without modifying state.
Register the pentest MCP server in PolicyLayer and add a rule for fetch_nmap_results: 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 pentestMCP. Nothing to install.
fetch_nmap_results 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 fetch_nmap_results 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 fetch_nmap_results. 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.
fetch_nmap_results is provided by the pentest MCP server (ramkansal/pentestmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 pentestMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 pentestMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.