You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enable Safe Default Rate Limiting for Scanning Tools
ARTEX already has a noise governor, which is a good addition, but I noticed that it is disabled by default.
There are also some important limitations documented in the README:
Raw scanners such as Nmap are not paced by the governor.
Commands that bypass the proxy can avoid its rate controls.
With traffic capture disabled, Bash-launched tools are not paced.
Some limits, such as retries and in-flight request caps, only apply to ARTEX's own requests.
Considering that multiple autonomous workers can execute tools concurrently, this could result in considerably more traffic than an operator expects.
I'd like to see more consistent rate enforcement across all scanning tools, with conservative defaults that prioritize target stability.
Expected outcome: All agent-initiated scanning activity should operate within predictable traffic limits, regardless of which tool initiates the request.
This is a feature request to extend ARTEX's noise governor so all agent-initiated scanning tools, including raw scanners and proxy-bypassing or Bash-launched commands, are consistently rate-limited with conservative defaults that prioritize target stability.
🤖 automated reply from the repo bot. A human maintainer reads everything. Ping me in any comment with @artex-bot.
Activity
github-actions commentedon Nov 20, 2026
This is a feature request to extend ARTEX's noise governor so all agent-initiated scanning tools, including raw scanners and proxy-bypassing or Bash-launched commands, are consistently rate-limited with conservative defaults that prioritize target stability.
🤖 automated reply from the repo bot. A human maintainer reads everything. Ping me in any comment with
@artex-bot.