# Read a key at call time with an identity that can reach only that agent's keys

> Read a key at call time with an identity that can reach only that agent's keys: 9 companies fully do it, 3 with a limit, 14 carry the tag. Every listing in Secrets & credential vaults with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/secrets.scoped-read/
- Markdown: https://www.anchorterminal.com/niches/secrets.scoped-read/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/secrets.scoped-read/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/secrets.scoped-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

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 9 | 3 | 14 | 26 | 9 |

## What counts as done

The agent's identity reads its own secret by name in one call, a read of any other secret returns a typed 403, and the identity needs no admin or list permission outside its scope.

How agents ask for it: give the agent read access to the staging keys only; how should the agent get the database password; set up a service account for this agent

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **1Password service accounts, SDKs and Environments MCP (AgileBits Inc. (doing business as 1Password))**: A service account gets read_items on named vaults only, and op read or secrets.resolve fetches op://vault/item/field in one call. Permissions are immutable, so narrowing means a new account; Teams gets 1,000 reads an hour per token.
- **Akeyless (SecretlessAI and MCP server) (Akeyless Security Ltd.)**: Access roles grant read on a path such as /path/to/folder/* with list as a separate capability and explicit deny rules, and get-secret-value fetches by path in one call. The free plan allows 5 clients.
- **AWS Secrets Manager (Amazon Web Services, Inc. (Amazon Web Services EMEA SARL and other regional entities by account location))**: An identity policy can allow secretsmanager:GetSecretValue on one secret ARN with no ListSecrets, and reads go by name or ARN in one call; acc-06 keeps everything else out of the agent role's reach. Each call is billed.
- **Azure Key Vault (Microsoft Corporation)**: Key Vault Secrets User can be assigned on one vault or one secret, Key Vault Reader returns metadata only, and Get Secret reads by name in one call. acc-08 relies on the agent's identity against the vault deciding access.
- **Doppler (Doppler Technologies, Inc.)**: A service token is read-only on a single config, and doppler secrets get NAME --plain reads one secret by name. Developer allows 120 secret reads a minute, with 429 and rate-limit headers.
- **Google Cloud Secret Manager (Google LLC (Google Cloud EMEA Limited and other regional entities by billing address))**: roles/secretmanager.secretAccessor can be granted on a single secret, carrying only versions.access plus project get and list, and AccessSecretVersion reads a named secret's version in one call. IAM conditions can add an expiry.
- **Infisical (Infisical, Inc.)**: Privileges take read and readValue actions with environment and secret-path conditions, and a machine identity reads one secret by key in one call. acc-13 found the additional-privileges control missing for one agent-proxy identity.
- **Keeper Secrets Manager (Keeper Security, Inc.)**: An application sees only the records and folders shared to it, each device has its own revocable configuration, and keeper://<TITLE|UID>/field/password reads by title or UID in one call. acc-16's 2024 title-lookup failure is closed.
- **Phase (Phi Security Inc.)**: A service account has its own role and is granted chosen apps and environments, and the secrets endpoint filters by environment, path and key, so one read fetches one named secret. The REST API needs server-side encryption on the app.

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

- **Bitwarden Secrets Manager (Bitwarden Inc. (terms name 8bit Solutions LLC, wholly owned by Bitwarden Inc.))**: A machine account gets Can read on chosen projects only, but bws secret get takes the secret's UUID, so the agent must list the project first; the CLI docs still show bws secret get <SECRET_ID>, as acc-14 complained.
- **HashiCorp Vault + Vault MCP Server (HashiCorp, Inc. (an IBM company))**: Path policies are deny by default and can grant read on one path without list, read by path in one call. The MCP server's KV tools first read sys/mounts, so a path-scoped token gets 403 (acc-15, still open).
- **Pulumi ESC (Pulumi Corporation)**: environment:open is granted per environment and resolves all its secrets, and pulumi env open <env> <path> returns one value. Narrow team or organisation tokens need Essentials or Pro; the free edition has only personal tokens with all the user's rights.

## What stops agents finishing

- tool needs a broader permission (sys/mounts) than the secrets themselves
- secrets fetchable only by UUID, so the agent must list first
- no way to create a service account without a signed-in person
- permissions fixed at creation and cannot be narrowed later

## Around it

Before: agent-harnesses.start-run. After: code-sandboxes.run-command, inference.call-model.

## Where this comes from

Weight 26 of 100 in Secrets & credential vaults: 9 of 27 accounts (1Password vault scoping, AWS IAM role, Azure Key Vault identity, Infisical, Bitwarden and Keeper lookup, Vault MCP sys/mounts); the most described job

As data: https://www.anchorterminal.com/api/v1/use-cases/secrets.scoped-read.json, or the MCP tool get_use_case with id secrets.scoped-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
