No user-submitted related servers found.
Scored across 39 tools
Most tools are clearly separated by scanner domain (GuardDuty vs Inspector vs Security Hub) or by output format. The main risk is the report matrix — generate_report / generate_html_report / generate_mlps3_report / generate_mlps3_html_report / generate_hw_defense_report / generate_maturity_report — plus three similarly named cloud compliance scanners (config_rules vs config_compliance vs rms_compliance) that could be misselected. Descriptions do disambiguate in each case, so confusion is possible but recoverable.
Strong snake_case verb_noun convention throughout: scan_*, list_*, generate_*_report, get_*, save_results. Minor deviations break the pattern: detect_services is a scanner but lacks the scan_ prefix, and save_results / prioritize_vulnerabilities omit the resource object implied elsewhere. Overall predictable and readable.
39 tools is heavy for a single server, inflated by ~22 single-scanner wrappers that duplicate what scan_all and scan_group already provide. Each scanner is arguably useful for targeted runs, and the aggregate tools mitigate the surface, but the count sits above a comfortable ceiling and pushes agents toward scanning everything by default.
Covers the full read-only audit lifecycle: discovery (list_modules, list_groups, list_org_accounts), scanning (scan_all, scan_group, per-service scanners), triage (prioritize_vulnerabilities, scan_ecr_image_cve), and reporting (Markdown/HTML/MLPS3/HW-def/report-saving). Minor gaps: no tool to list or retrieve previously saved scan results/reports, and no scan history or scheduling, so follow-up sessions must re-scan.