# Rotate a key or revoke an identity while agents are running

> Rotate a key or revoke an identity while agents are running: 1 companies fully do it, 11 with a limit, 12 carry the tag. Every listing in Secrets & credential vaults with the reason and a source.

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

One company's docs show a full fit.

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

## What counts as done

After rotation the next read returns the new value without a restart, the old value stops working within a stated window, and after revocation the identity's next read fails with no cached fallback serving values.

Measured, for our own tests: the read after revocation fails within 60 seconds.

How agents ask for it: the key leaked, rotate it; revoke the agent's token now; roll the database password without restarting the agent

## Does the job

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

- **HashiCorp Vault + Vault MCP Server (HashiCorp, Inc. (an IBM company))**: Dynamic secrets carry leases; revoking one invalidates it immediately and deletes cloud keys such as AWS ones at revoke. Agent re-renders on change and restarts the supervised process by default.

## 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))**: References resolve at each read, so a changed value arrives on the next read, but op run fixes values at child start. Tokens can be revoked; no page states how long a revoked token keeps reading. No managed rotation.
- **Akeyless (SecretlessAI and MCP server) (Akeyless Security Ltd.)**: Rotated secrets cover databases, clouds and SaaS, with graceful rotation, and UID tokens can be revoked with a 60-minute default TTL. No page states how long a revoked identity or the Gateway cache keeps serving values.
- **AWS Secrets Manager (Amazon Web Services, Inc. (Amazon Web Services EMEA SARL and other regional entities by account location))**: Managed rotation covers the RDS family, and other secrets need a Lambda function you write; AWSPREVIOUS keeps the last version readable. Caching clients serve values until their TTL, and no revocation window is stated.
- **Azure Key Vault (Microsoft Corporation)**: No managed rotation for secrets; a near-expiry event triggers your own Function. Removing a role assignment takes several minutes to refresh, beyond the 60-second bar.
- **Bitwarden Secrets Manager (Bitwarden Inc. (terms name 8bit Solutions LLC, wholly owned by Bitwarden Inc.))**: Reads are live, so an edited value arrives on the next read, but there is no rotation, and a revoked token keeps reading for up to an hour on authenticated machines, longer through reused state files.
- **Doppler (Doppler Technologies, Inc.)**: Rotation with a two-secret strategy is Team and Enterprise only, and doppler run fixes values at start. The fallback snapshot can serve values without the API, and no revocation window is stated.
- **Google Cloud Secret Manager (Google LLC (Google Cloud EMEA Limited and other regional entities by billing address))**: Rotation is a SECRET_ROTATE message to Pub/Sub that your subscriber must act on. Removing an IAM grant typically takes 2 minutes and can take 7 or longer, past the 60-second bar.
- **Infisical (Infisical, Inc.)**: A revoked Agent Vault session stops getting credentials within one 60-second poll, but the proxy keeps cached session data for five polls if Infisical is unreachable. run --watch restarts the child on change; it does not update in place.
- **Keeper Secrets Manager (Keeper Security, Inc.)**: Revoking a device configuration cuts access immediately, but the optional SDK cache serves the last secrets when Keeper is unreachable, and rotation needs KeeperPAM with a Gateway.
- **Phase (Phi Security Inc.)**: Rotating secrets mint a new credential and revoke the old one after a stated revocation delay, picked up on next read. Rotation needs Pro, and how fast a revoked service account token stops reading is not stated.
- **Pulumi ESC (Pulumi Corporation)**: Rotators keep two valid secrets and each open reads the current one, but rotation runs only on schedule or command and no doc states how fast a revoked token stops opening environments.

## What stops agents finishing

- revoked token keeps working up to an hour on authenticated machines (Bitwarden)
- CLI fallback file serves values after revocation (Doppler)
- rotation outside managed databases needs a function the owner writes
- leak notice lost in an inbox

## Around it

Before: security-intelligence.leak-alert, email.read-inbox. After: notifications.push.

## Where this comes from

Weight 9 of 100 in Secrets & credential vaults: 3 of 27 accounts (hosting-provider leak, CI leak, moving off env vars); held up by the category test and the Bitwarden, Doppler and Trigger.dev weaknesses on revocation lag

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