{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/secrets.approve-read/",
    "json": "https://www.anchorterminal.com/niches/secrets.approve-read/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/secrets.approve-read/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/secrets.approve-read/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 5 | 28 | 5 | 2 |\n\n## What counts as done\n\nThe 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.\n\nMeasured, for our own tests: the approval releases it within 60 seconds.\n\nHow agents ask for it: ask me before the agent uses the production key; approve this secret from my phone\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n\n- 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.\n- not this job: Azure Key Vault (Microsoft Corporation): No approval step pauses a secret read; access is granted by role assignment alone.\n- 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.\n- not this job: Doppler (Doppler Technologies, Inc.): Change requests gate edits to secrets, not reads; no approval for a read is documented.\n- 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.\n- 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.\n- not this job: Phase (Phi Security Inc.): No approval step for reading a secret is documented.\n\n## What stops agents finishing\n\n- service accounts have no approval step, only desktop-app biometric unlock\n- approval tied to a desktop session on the same machine\n\n## Around it\n\nBefore: secrets.scoped-read. After: human-in-the-loop.approve-action.\n\n## Where this comes from\n\nWeight 5 of 100 in Secrets \u0026 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\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Have a person approve a sensitive read at run time",
        "url": ""
      }
    ],
    "description": "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 \u0026 credential vaults with the reason and a source.",
    "facts": null,
    "h1": "Have a person approve a sensitive read at run time",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/secrets.approve-read/",
    "published": "",
    "section": "agents",
    "title": "Have a person approve a sensitive read at run time | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/secrets.approve-read/"
  },
  "tokens": {
    "markdown": 1250,
    "slim": 280
  },
  "version": 1
}
