| Framework Home | Cross-Pillar Governance | AISM | NEXUS | Dashboard |
| Previous: ← NEXUS | Next: Gateway / Runtime Enforcement → |
A static scan score is not organizational maturity or a technology contribution
score. Pattern matches and source availability do not prove runtime enforcement.
The Technology Contribution Profile
records static evidence as evidences or addresses where justified, with
assurance assigned to the specific claim.
Independent validation requires an identified evaluator and material results;
a clean scan or translated report supplies neither automatically.
| Surface | Tool | When |
|---|---|---|
| Design-time | Skills + AI SAFE² MCP Server | While designing and building |
| Pre-commit / CI | Scanner, you are here | Before code reaches production |
| Runtime | Gateway / enforcement components | During execution |
The scanner evaluates code and configuration against AI SAFE² patterns. It is a static-analysis aid, not proof of full control conformance.
AI SAFE² v3.1 keeps the 161-control core framework taxonomy and adds a machine-readable CP.5.MCP profile with MCP-1 through MCP-19.
The scanner currently exposes 64 detection rules:
Profile rules are grouped because several MCP controls require runtime evidence and cannot be proven by a one-pattern-per-control static check. The v3.1 release preserves existing detections rather than deleting rules merely to satisfy an outdated expected count.
server/discover is optional under MCP 2026-07-28; the scanner does not require it.Mcp-Session-Id must not be treated as identity or the authorization boundary.INFO) until deployment-specific authorization behavior can be proven.| Category | Representative controls |
|---|---|
| Secrets and NHI | P1, CP.4, MCP-9 |
| Injection and untrusted content | P1, S1.6, MCP-2 |
| Memory and persistence governance | S1.5, A2.6, MCP-12/MCP-16 |
| Unsafe execution | P1.T2.1, MCP-1 |
| Server and binary provenance | P1.T1.9, MCP-3/MCP-4 |
| Audit gaps | A2.5, P4.T8.3, MCP-5 |
| Tool input validation | P1.T1.1, MCP-6 |
| Trust establishment | CP.4, MCP-7 |
| Economic ceilings | F3.2, MCP-8 |
| Delegation lineage | CP.9, MCP-10 |
| Catalog/schema drift | A2.6, MCP-11/MCP-18 |
| Protocol assertion/replay integrity | MCP-15/MCP-17 |
| Authorization-chain integrity | MCP-19, advisory |
| Missing HEAR / CRT | CP.10, CP.8 |
| Agent spawning | CP.9 |
pip install -r scanner/requirements.txt
# Scan current directory
python -m scanner.cli scan .
# Scan with a tier threshold
python -m scanner.cli scan ./my-agent --tier Tier2
# JSON and SARIF report
python -m scanner.cli scan . --report both --output report.json
# Fail CI when score is below threshold
python -m scanner.cli scan . --fail-under 80
Score: static-analysis score derived from finding severity.
ACT estimate: inferred autonomy signals used to surface governance gaps such as HEAR, CRT, and replication governance.
Governance gaps: structural indications that required ownership, logging, fail-safe, delegation, or protocol controls may be absent.
Framework mappings: findings are enriched from the core control taxonomy when data is available. MCP profile metadata is maintained separately from the 161 core controls.
Static findings are evidence inputs. They are not a substitute for runtime conformance testing.
The v3.1 MCP rules live at:
The machine-readable profile they correspond to is:
skills/mcp/data/mcp-profile-v3.1.json
The canonical normative specification is:
Regression tests enforce:
server/discover presence rule;name: AI SAFE2 Security Scan
on: [push, pull_request]
jobs:
scan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: "3.12"
- run: pip install -r scanner/requirements.txt
- name: AI SAFE2 v3.1 scan
run: |
python -m scanner.cli scan . \
--tier Tier2 \
--report both \
--output ai-safe2-report.json \
--fail-under 70
The current data model separates:
skills/mcp/data/ai-safe2-controls-v3.0.json stable 161-control core taxonomy
skills/mcp/data/mcp-profile-v3.1.json CP.5.MCP v3.1 profile overlay
This is intentional. v3.1 changes the MCP profile without pretending the core framework grew from 161 to 180 controls.
scanner/
├── README.md
├── cli.py
├── scanner.py
├── report.py
├── tests/
│ └── test_v31_mcp_profile.py
└── rules/
├── __init__.py
├── base.py
├── p1_sanitize.py
├── p2_audit.py
├── p3_failsafe.py
├── p4_monitor.py
├── p5_evolve.py
├── cross_pillar.py
└── mcp_profile.py
| Previous | Current | Next |
|---|---|---|
| NEXUS | Scanner | Gateway |
| Framework Home | Cross-Pillar Governance | AISM | NEXUS | MCP Profile | Dashboard |
AI SAFE² v3.1 · Cyber Strategy Institute