No user-submitted related servers found.
Scored across 36 tools
Each tool clearly targets a distinct operation: list modules/groups/accounts, run specific scanners per security domain, generate specific report types, or save/setup. Even the many scan_* tools are each named for a unique security check (e.g., scan_ssl_certificate vs scan_dns_dangling), and their descriptions explicitly state what they scan. The grouping tools (scan_all, scan_group, scan_and_report) are distinct in their purpose and input/output.
Tool names follow a consistent verb_noun pattern: list_* for listing, scan_* for scanning, generate_* for report generation, and get_* for retrieval. Exceptions like save_results and get_setup_template still follow the verb_noun structure. All names use snake_case consistently.
With 36 tools, this is on the heavier side, but the broad scope of AWS security scanning justifies the count. Each scanner represents a distinct security domain, and report generation tools cover different formats and compliance frameworks. However, the sheer number might overwhelm an agent, especially since many scan_* tools are repetitive in pattern.
The tool surface covers the full lifecycle: listing available modules/groups, discovering org accounts, running individual scans, running grouped scans, generating multiple report types (Markdown, HTML, MLPS, HW defense, maturity), and saving results. Minor gaps include lack of a get_results or delete_report tool, but for a security scanning server, the coverage is quite complete.