# Have a person approve a sensitive read at run time (slim)

> Have a person approve a sensitive read at run time: 0 companies fully do it, 5 with a limit, 28 carry the tag. Every listing in Secrets & credential vaults with the reason and a source.

- Full: https://www.anchorterminal.com/niches/secrets.approve-read/index.md (~1,250 tokens) · this version ~280 tokens · JSON https://www.anchorterminal.com/niches/secrets.approve-read/index.json · canonical https://www.anchorterminal.com/niches/secrets.approve-read/
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-15
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all. Full fit: 0 companies, with a limit: 5, tagged: 28. Weight 5, 2 accounts.

Done when: The read pauses, the person gets a prompt on a phone or chat naming the agent and the secret, and an approval releases the value or the brokered call while a denial or no answer in the set time returns a typed refusal.
caveat: 1password (AgileBits Inc. (doing business as 1Password))
caveat: akeyless (Akeyless Security Ltd.)
caveat: hashicorp-vault (HashiCorp, Inc. (an IBM company))
caveat: keeper-secrets-manager (Keeper Security, Inc.)
caveat: pulumi-esc (Pulumi Corporation)

Data: https://www.anchorterminal.com/api/v1/use-cases/secrets.approve-read.json
