Ranked #6 of 79/18 · Last reviewed

AppSec scanning

Static analysis, dependency (SCA) and secrets scanning of code and pull requests, finding vulnerabilities and leaked secrets in what agents and people wrote.

Verdict: Necessary for the code agents write; blind to the actions they take to write it.

Who it suits

Every team shipping code; it is the check on the output, whoever wrote it.

Examples

SAST, SCA and secrets scanners in CI and the IDE

Cost

Varies by scanner and seat count; several have free tiers: check each vendor's pricing page.

Pairs with

An AASB for the actions; AppSec for the code.

How it handles MCP connections
  • Discovery: Can find MCP configuration files committed to repositories.
  • Control: None at runtime.
  • Record: Scan results for code and configuration.

Strengths

  • Catches vulnerable code and leaked secrets before merge
  • Already in most CI pipelines
  • Evidence of what was scanned and fixed

Limits

  • Runs after the code is written; the agent's commands have already run
  • Never sees terminal commands, file reads or MCP calls
  • A secret sent to a model provider as context never reaches the repo to be scanned

Scores, with reasons

Each criterion is scored 0 to 3 as defined on the criteria page.

CriterionScoreWhy
Visibility 1Sees the code an agent produced, not the agent or its session.
Enforcement 1Gates a merge, after every command has already run.
Developer friction 2Familiar to developers, with the usual false positives to triage.
Coverage of terminal and MCP actions 0Does not see terminal commands or MCP calls.
Audit evidence 2Scan results and fixes per repository, not records of agent activity.
Deployment effort 3Usually already running in CI.
Total9/18Ranked #6 of 7. See the full table.
Other approaches