# Have a person approve a sensitive read at run time

> 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.

- Canonical: https://www.anchorterminal.com/niches/secrets.approve-read/
- Markdown: https://www.anchorterminal.com/niches/secrets.approve-read/index.md (~1,250 tokens)
- Slim: https://www.anchorterminal.com/niches/secrets.approve-read/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/secrets.approve-read/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 5 | 28 | 5 | 2 |

## What counts as done

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.

Measured, for our own tests: the approval releases it within 60 seconds.

How agents ask for it: ask me before the agent uses the production key; approve this secret from my phone

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **1Password service accounts, SDKs and Environments MCP (AgileBits Inc. (doing business as 1Password))**: The Environments MCP and OpenShell connections show an authorisation prompt in the desktop app, on the same machine. Service accounts have no approval step, and acc-04 wants a phone approval that does not exist.
- **Akeyless (SecretlessAI and MCP server) (Akeyless Security Ltd.)**: Request Access lets an identity ask for temporary read on an item, approved in the Event Center or ServiceNow, with a 60-minute default grant. It is a separate request, not a paused read with a deny-on-timeout.
- **HashiCorp Vault + Vault MCP Server (HashiCorp, Inc. (an IBM company))**: Control groups return a wrapping token instead of the data until named authorisers approve, and the wrapping TTL bounds the wait. Enterprise only, and approval goes through the Vault API or UI, not a phone or chat prompt.
- **Keeper Secrets Manager (Keeper Security, Inc.)**: The MCP server asks for confirmation in the client before returning an unmasked value, unless --auto-approve is set. That is the chat client's session, with no timeout or phone prompt; SDK and ksm reads have no approval.
- **Pulumi ESC (Pulumi Corporation)**: Open approvals (Pro and Enterprise) make a user submit an open request with a reason and duration that reviewers approve before access. It is a request workflow ahead of the read, with no stated timeout or phone prompt.

- not this job: AWS Secrets Manager (Amazon Web Services, Inc. (Amazon Web Services EMEA SARL and other regional entities by account location)): Secrets Manager has no step that pauses a read for a person's approval; access is decided by IAM policy alone.
- not this job: Azure Key Vault (Microsoft Corporation): No approval step pauses a secret read; access is granted by role assignment alone.
- not this job: Bitwarden Secrets Manager (Bitwarden Inc. (terms name 8bit Solutions LLC, wholly owned by Bitwarden Inc.)): No approval step for a machine account's read is documented.
- not this job: Doppler (Doppler Technologies, Inc.): Change requests gate edits to secrets, not reads; no approval for a read is documented.
- not this job: Google Cloud Secret Manager (Google LLC (Google Cloud EMEA Limited and other regional entities by billing address)): No approval step pauses an AccessSecretVersion call; access is IAM only.
- not this job: Infisical (Infisical, Inc.): Agent Vault hooks answer allow or deny within 3 seconds, too short for a person, and temporary access is granted ahead of time, not by pausing a read.
- not this job: Phase (Phi Security Inc.): No approval step for reading a secret is documented.

## What stops agents finishing

- service accounts have no approval step, only desktop-app biometric unlock
- approval tied to a desktop session on the same machine

## Around it

Before: secrets.scoped-read. After: human-in-the-loop.approve-action.

## Where this comes from

Weight 5 of 100 in Secrets & credential vaults: 2 of 27 accounts (1Password remote approval wish, runtime supervision); no listing has it for machine reads, so it is a gap rather than a job done today

As data: https://www.anchorterminal.com/api/v1/use-cases/secrets.approve-read.json, or the MCP tool get_use_case with id secrets.approve-read. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
