Disconnect a platform
Disconnecting removes a connection’s credential from the vault straight away — any agent that relied on it loses access on its next call.
How
Platforms → Connections → click the connected platform’s card (Manage ›) to open its connection panel → click Disconnect on the connection you want to remove.
The row asks inline: Remove this connection? Click Yes, remove to proceed, or Cancel.
If the platform has more than one connection, disconnect each one you want gone. Removing the default connection promotes another one to default.
What happens
- The encrypted credential for that connection is removed from AgentValet’s vault
- Grants that were pinned to that specific connection are deleted
- Platform-wide grants (not pinned to a connection) are kept. If no connection is left, the agent page shows those grants with a Not connected badge, and calls fail until you connect the platform again
- For an MCP server you added yourself, removing its last connection also removes the server from your catalog (unless an agent still holds a grant on it)
AgentValet does not revoke the token at the provider, and no audit row is written for the disconnect. If the credential leaked, also revoke it on the platform’s own side.
When to disconnect
- The credential leaked or you’re rotating
- You’re shutting down an integration entirely
- An employee left and the platform was theirs
For temporary issues (the token expired and you want to refresh, not remove): reauth instead.
Reconnecting later
A disconnected platform isn’t deleted — its catalog entry is still there. Connecting again is the same as the first time: OAuth or API-key flow, fresh credential, fresh encryption.
Platform-wide grants start working again as soon as the platform is reconnected. Grants that were pinned to the removed connection are gone — re-grant them on each agent’s detail page.