ash-mcp
ASH MCP security scanning workflow
ASH (Automated Security Helper) combines code, infrastructure, secrets, and dependency scanners behind one MCP interface. Its MCP server runs a scan in the background: you start it, poll it until it ends, then read the results. This skill assumes the server is connected; the plugin that ships this skill configures it.
The server scans on the machine it runs on, always in local mode, with the scanner tools installed there. The project's ASH config, or the config profile the session selected, chooses the scanners and the severity thresholds. Use list_scanners to inspect the installed scanner catalog. No tool argument chooses scanners, and run_ash_scan's severity_threshold can only make the config's threshold stricter.
Run a scan
- Call
run_ash_scanwithsource_dirset to the absolute path of the project. It returns at once with ascan_idandstatusrunning. Keep thescan_id. - Call
get_scan_progresswith thatscan_idabout every 5 seconds untilis_completeis true. It is true for every way a scan ends:statusis thencompleted,incomplete,failed, orcancelled. - When
results_availableis true, read the results fromoutput_directory, the absolute path in the progress response. It is.ash/ash_outputinsidesource_dir.
Step 1 — Start the scan
Call run_ash_scan with the absolute path to the project. The call returns immediately with a scan_id.