Niches · Secrets & credential vaults
Rotate a key or revoke an identity while agents are running
One company's docs show a full fit.
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. No docs we read state these figures, so they don't count against a listing here.
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 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| HashiCorp Vault + Vault MCP Server C 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. source |
Does the job, with a limit 11
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.
| Listing | Why |
|---|---|
| 1Password service accounts, SDKs and Environments MCP BB 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. source |
| Akeyless (SecretlessAI and MCP server) BB 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. source |
| AWS Secrets Manager A 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. source |
| Azure Key Vault BB 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. source |
| Bitwarden Secrets Manager C 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. source |
| Doppler BB 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. source |
| Google Cloud Secret Manager BB 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. source |
| Infisical AA 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. source |
| Keeper Secrets Manager B 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. source |
| Phase B 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. source |
| Pulumi ESC BB 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. source |
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
The same as data: /api/v1/use-cases/secrets.rotate-revoke.json, or the MCP tool get_use_case with id secrets.rotate-revoke. Other jobs in this category: /api/v1/niches?category=secrets.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.