Skip to content

Rate limiting #422

Open
Open

Description

@youssefmedhatl

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.

Activity

  1. github-actions commented on Nov 20, 2026

    @github-actions

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions