Low Risk

fetch_nuclei_results

Non-blocking fetch for Nuclei scan results:

How to control fetch_nuclei_results ↓

AI agents call fetch_nuclei_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.

Low Risk

Although this tool retrieves results from a penetration testing security scanner (Nuclei), the tool itself performs no modifications, deletions, or execution. It only reads/fetches scan results.

From the tool's definition Tool is described as a 'Non-blocking fetch for Nuclei scan results' — the verb 'fetch' and the retrieval operation indicate this retrieves or queries data without side effects.

Documented attack patterns abuse exactly the kind of access fetch_nuclei_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_nuclei_results:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_nuclei_results": {}
  }
}

fetch_nuclei_results is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register pentestMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the fetch_nuclei_results tool do? +

Non-blocking fetch for Nuclei scan results:. It is categorised as a Read tool in the pentestMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_nuclei_results? +

Register the pentest MCP server in PolicyLayer and add a rule for fetch_nuclei_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.

What risk level is fetch_nuclei_results? +

fetch_nuclei_results is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fetch_nuclei_results? +

Yes. Add a rate_limit block to the fetch_nuclei_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.

How do I block fetch_nuclei_results completely? +

Set action: deny in the PolicyLayer policy for fetch_nuclei_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.

What MCP server provides fetch_nuclei_results? +

fetch_nuclei_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.

Enforce policy on every pentestMCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.