---
title: "A Risk Label Does Not Give a Tool Permission"
canonical: https://dxdev.com/blog/2026-06-05_capability-before-autonomy/
datePublished: 2026-06-05
---
Calling a task low risk does not create the access, evidence, or reversal path needed to perform it safely.

## The practical check

Ask what the tool is actually allowed to read, suggest, prepare, or change. The answer should come from a capability boundary, not a label.

## Where AI fits

AI can map a task into read, draft, suggest, and action capabilities with evidence for each boundary.

## The human decision

People grant authority, review exceptions, and decide when a capability should expand.

## The lesson

Give a tool the narrowest capability that the evidence and approval process support, then expand authority only when people can account for the consequences.

Bounded agent authority is set out in the Build Log companion through capability evidence, access limits, and a reversal route.