Evaluating Human-AI Safety: A Framework for Measuring Harmful Capability Uplift
Organizations: Massachusetts Institute of Technology, Cambridge, USA
Abstract
Current frontier AI safety evaluations emphasize static benchmarks, third-party annotations, and red-teaming. In this position paper, we argue that AI safety research should focus on human-centered evaluations that measure harmful capability uplift: the marginal increase in a user's ability to cause harm with a frontier model beyond what conventional tools already enable. We frame harmful capability uplift as a core AI safety metric, ground it in prior social science research, and provide concrete methodological guidance for systematic measurement. We conclude with actionable steps for developers, researchers, funders, and regulators to make harmful capability uplift evaluation a standard practice.
Figures & tables
Appendix figures & tables1 asset
Supplementary material from the paper’s appendix.
Appendix
| Study | Task(s) | Design | Sample Size | Evaluation Criteria | Results | Data |
| [ 4 ] | Draft bioweapons acquisition plans | Between-subjects | Not provided | Task score | (significant) | No |
| [ 6 ] | Draft bioweapons acquisition plans | Between-subjects | Not provided | Task score | (Opus 4) (significant) (Sonnet 4) (not significant) (Sonnet 3.7) (not significant) | No |
| [ 47 ] | Plan bioweapons attacks | Between-subjects | 15 teams (4-6 per condition) | Viability score | (not significant) | No |
| [ 53 ] | Research tasks for biological-threat creation | Between-subjects | 100 participants (25 per condition) | Accuracy Completeness Innovation Time Difficulty | (not significant) | Yes |
| [ 7 ] | Reconstruct a virus | Not provided | Not provided | Task score | (Opus 4.5) (Opus 4) (Sonnet 3.7) | No |
| [ 5 ] | Answer CBRN risk-relevant questions | Between-subjects | 30 participants (10 per condition) | Accuracy | No data (not significant) | No |
AI Safety Evaluation
AI Safety Evaluation studies how to test whether AI systems avoid harmful behavior and remain reliable across users, tasks, and deployment settings.
See all 141 papers