AI agents invoke nuclei_scan to trigger actions in Redteam. 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.
Nuclei executes active vulnerability scanning using templates against external targets. This triggers real network requests and probe attempts against systems, making it an Execute-category tool. Running on a Kali Linux container explicitly for penetration testing increases the blast radius — misuse could constitute unauthorized scanning of third-party systems, hence high severity.
From the tool's definition Run Nuclei template-based vulnerability scanner against a target
Attacks that exploit this kind of access
Run Nuclei template-based vulnerability scanner against a target. It is categorised as a Execute tool in the Redteam MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Redteam MCP server in PolicyLayer and add a rule for nuclei_scan: 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 Redteam. Nothing to install.
nuclei_scan 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 nuclei_scan 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 nuclei_scan. 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.
nuclei_scan is provided by the Redteam MCP server (samirjani03/redteam-mcp). 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 →