Vulnerator AI 1.3.0

What's new

Opt-in scope-guard for kali_run / kali_exec. A deterministic (code, not prompt) layer that validates the DESTINATION of each raw-shell action before executing it. It lives inside the Kali MCP, in front of the two raw-shell runners; it does not touch the cloud tools (Prowler/Pacu/IAM) or the browser MCP.

How it works

• Opt-in. With no scope.json present (path via SCOPE_FILE, default /scope/scope.json), behavior is identical to before — no gate. The guard activates only when the file exists and contains enabled: true.
• Fail-closed when active. Hermes must declare the new optional targets argument (the IP/host/URL the command touches). Any destination outside the allowed scope — or in deny — blocks the whole execution with a structured SCOPE_VIOLATION error without running. If targets is not declared while the scope is active, the call is blocked.
• Validation. IP-against-CIDR plus literal hostname match (no DNS) with optional ports; deny takes priority over allow. A best-effort parse of the command is an extra belt that can only block, never approve.
• Auditable. Each violation is logged into the engagement findings store as a discarded SCOPE_VIOLATION record.
• Kill-switch. SCOPE_ENFORCE=0 force-disables the guard even if the file says enabled: true.

Zero new dependencies (stdlib json/ipaddress/urllib.parse). New scope.example.json template, a commented bind-mount in docker-compose.yml, and a README section document how to turn it on.

Default behavior (no scope.json) is unchanged.

Full Changelog: v1.2.0...v1.3.0