Niches · Agent auth & delegated access
Revoke an agent's access and have it stop
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
After revocation the agent's next call fails with a typed revoked error, the stored refresh token is gone, and the grant is also revoked at the provider where it has an endpoint.
Measured, for our own tests: the next call fails within 60 seconds of revocation. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: cut off the agent's access to my Drive
, revoke everything this agent was given
, disconnect my account
Does the job, with a limit 12
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 |
|---|---|
| Aembit BB Aembit, Inc. | Revoking a session stops its refresh tokens and denies requests within about a minute, logged as McpSessionExpiredOrRevoked. It does not revoke the user's grants at the MCP server, and the access token is still accepted by the gateway until expiry. source |
| Arcade.dev B Arcade AI, Inc. | DELETE /v1/admin/user_connections/{id} removes one user's connection. The docs read say nothing about revoking at the provider or how quickly a running tool stops. source |
| Auth0 for AI Agents (Token Vault) BB Okta, Inc. | Deleting a connected account removes its tokens from Token Vault, but Auth0 says this does not revoke at the provider and the refresh token could still mint access tokens until revoked there. source |
| Cloudflare Workers OAuth Provider A Cloudflare, Inc. | RFC 7009 revocation works on the token endpoint and deleting a client revokes its grants, but an open issue of 28 October reports revocation is not final under KV eventual consistency and can resurrect a deleted grant. source |
| Descope Agentic Identity Hub A Descope, Inc. | Revoking an agentic identity, in the console or by API, invalidates its current tokens and ends its sessions without deleting the client. Timing and revocation at the third-party provider are not stated. source |
| Keycard D Keycard Labs, Inc. | Revoking a grant in the Console or API stops the next credential, but there is no per-token kill switch, and for brokered providers the last token keeps working at the provider, about 8 hours for GitHub. source |
| Microsoft Entra Agent ID BB Microsoft Corporation | Agent identities can be deleted through Graph, separately from users. Revoking one user's delegated grant, and how long issued tokens keep working, is not covered in the Agent ID pages. source |
| Nango B Nango Inc | Terminating an agent session makes its MCP server answer 401 at once, and connections can be deleted by API. The docs read do not say whether deleting a connection revokes the grant at the provider. source |
| Scalekit AgentKit BB ScaleKit, Inc. | delete_connected_account removes a user's connected account, and DISCONNECTED is a typed status. The docs read do not say whether deletion revokes at the provider or how fast running calls stop. source |
| Stytch Connected Apps B Twilio Inc. | Deleting a consent grant revokes every access and refresh token issued to that app for the user, and org settings can deny all connected apps. How quickly a revoked access token stops working at the MCP server is not stated. source |
| Vercel Connect BB Vercel Inc. | revokeToken, the CLI and dashboard call the provider's revocation endpoint where one exists; otherwise the token is deleted from Connect's store but may keep working at the provider until expiry. The SDK's in-process cache can also hold it. source |
| WorkOS Pipes and Agents B WorkOS, Inc. | Deleting a connected account removes stored access and refresh tokens, but WorkOS says it does not revoke access on the provider side; the user may need to disconnect at the provider. source |
Doesn't do this job 2
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Amazon Bedrock AgentCore Identity A Amazon Web Services, Inc. | No operation revokes one user's stored grant; forceAuthentication clears a refresh token on the next request, and AWS says it cannot detect revocation at the provider. source |
| Clerk MCP server B Clerk, Inc. | No revoke or disconnect call is documented beyond signing out in the client. source |
What stops agents finishing
- revocation endpoint advertised but not implemented
- no per-token kill switch, so a revoked grant lives until expiry
- deleting the connection does not revoke at the provider
- eventually consistent store keeps a revoked token working briefly
Around it
Before: agent-auth.connect-user-account. After: agent-auth.audit-agent-actions.
Where this comes from
Weight 5 of 100 in Agent auth & delegated access: 2 of 33 accounts (Cloudflare revocation endpoint and refresh rotation); held up because the category test and buyer check 4 rest on it and several listing weaknesses (Keycard, WorkOS, AgentCore, Vercel) concern it
The same as data: /api/v1/use-cases/agent-auth.revoke-access.json, or the MCP tool get_use_case with id agent-auth.revoke-access. Other jobs in this category: /api/v1/niches?category=agent-auth.
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.