Audit the authorization chain, not just the agent’s name. Identify the account, app or connector, user or tenant grant, and scopes the agent used; revoke the narrowest agent permission first, remove the underlying app grant when necessary, then verify tokens, sessions, audit events, and data already copied elsewhere. Revocation stops future use of that authorization, but it does not automatically erase information a third party already received.
What you are actually revoking
An AI agent usually does not receive a universal “agent credential.” It acts through an app, connector, OAuth consent grant, enterprise application, custom integration, or account link. The provider’s settings may therefore show the app or client rather than the agent that initiated a task.
As an Amazon Associate I earn from qualifying purchases.
Start by separating five different controls. They are related, but they do not produce the same result.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →| Control layer | What it stops or changes | What may remain |
|---|---|---|
| Agent-specific permission | Prevents a named AI agent from acting through a linked app where the provider exposes that setting. | The underlying account-to-app link or the app’s broader data grant may remain. |
| App account-data grant or OAuth consent | Removes the app’s authorized ability to call account APIs or access account data. | Previously copied data, active app sessions, and already-issued tokens may require separate follow-up. |
| Sign-in link, such as “Sign in with Google” | Stops the identity provider from supplying the sign-in relationship. | It does not necessarily delete the third-party account or information stored there. |
| Organization policy or administrator grant | Restricts or revokes access for a managed tenant, group, or application assignment. | Existing tokens, app sessions, and delayed audit-list updates may need separate action. |
| Third-party data deletion | Requests removal of data the app or agent already copied. | It does not revoke the account-provider authorization unless that grant is removed separately. |
The practical rule is simple: revoke the permission that lets the agent act, then inspect whether the app itself still has access. A “disconnect agent” action, when available, is not automatically equivalent to removing every app grant.
#1 Best Overall
- Requires 3 "AAA" batteries (included)
- Unit auto-locks for 30 minutes after 5 consecutive incorrect PINs
First, identify every account and integration
Write down the accounts the agent could reach before changing settings. Include personal and work email, cloud files, calendars, contacts, shopping and travel services, financial systems, support tools, and any internal application. An agent may have used more than one account during a single workflow.
Build an authorization inventory
- Account or tenant name and the affected user.
- Agent service and the task it was asked to perform.
- App, connector, enterprise application, MCP server, or client ID shown by the provider.
- Publisher or developer identity; do not rely on a familiar display name alone.
- Scopes or data categories, such as read mail, create files, manage calendar events, or delete data.
- Whether consent was granted by one user or approved for the whole organization.
- Approximate grant time, recent activity, and any run history held by the agent service.
Compare the displayed app identity and permissions with what you intended to configure. An app authorized to manage account data can have materially more power than one allowed only to sign you in. Google’s account-access guidance explains these distinctions and the consequences of removing access: Google Account Help: Share some access to your Google Account with third-party apps.
Preserve details if the connection is unexpected
Before deleting a suspicious entry, capture its name, client or app ID, scopes, consenting user, grant time, screenshots, and relevant agent-run identifiers. These details help an administrator or provider determine whether other users, credentials, or applications were affected.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsGoogle consumer accounts: revoke an agent and its app separately
Google currently exposes an agent-permission layer for some linked apps. The exact labels and availability can vary by account, device, and feature, so use the current Linked apps page rather than assuming every integration has the same controls.
Stop an AI agent from acting through a linked app
- Open Google Account and go to Linked apps.
- Find the relevant app, or filter the list for Agent access.
- Open the entry and select the specific agent permission.
- Choose Stop using and confirm.
- Record the time of the change and the permission that was removed.
Google states that removing an agent’s access stops the agent from completing tasks through the app, but does not disconnect or delete the Google Account link with that app. The provider documents this boundary in Manage links between your Google Account and apps from other developers.
Remove the app’s data access when it should have no account access
After stopping the agent, open the same app’s access details. If the app should no longer read or manage Google data, choose Remove access and confirm. Google notes that this can disable features that depend on the connection. Do not confuse the following actions:
- Stop using an agent: blocks that agent’s task execution through the linked app.
- Stop using Sign in with Google: removes the sign-in relationship.
- Remove access to account data: revokes the app’s authorized data or API access.
- Deleting an account at the third-party service: affects that service’s account and stored data, not necessarily the Google authorization by itself.
For the provider’s definitions and current navigation, use Google’s third-party app access help and Google’s linked-apps help.
Rank #2
- Auto-Fill Feature: Say goodbye to the hassle of manually entering passwords! PasswordPocket automatically fills in your credentials with just a single click.
- Internet-Free Data Protection: Use Bluetooth as the communication medium with your device. Eliminating the need to access the internet and reducing the risk of unauthorized access.
- Military-Grade Encryption: Utilizes advanced encryption techniques to safeguard your sensitive information, providing you with enhanced privacy and security.
- Offline Account Management: Store up to 1,000 sets of account credentials in PasswordPocket.
- Support for Multiple Platforms: PasswordPocket works seamlessly across multiple platforms, including iOS and Android mobile phones and tablets.
Disconnect a custom MCP server from Gemini
If Gemini was connected to a custom MCP server, open Gemini Settings, select Connected Apps, locate the server, and disconnect it. Google also documents unlinking the MCP server from the Google Account; that action revokes its permissions and disconnects the custom app from Gemini. Follow the platform-specific instructions at Connect and manage custom apps for Gemini Apps.
After disconnecting, inspect both Gemini’s Connected Apps list and the Google Account’s Linked apps page. A server can have a Gemini relationship and a separate account authorization, so checking only one screen can leave an app grant in place.
Google Workspace: handle user and tenant grants
In a work domain, an individual user’s consent may coexist with an administrator-approved, organization-wide grant. A user removing their own entry may not remove the enterprise application’s tenant access.
Administrator workflow
- In the Admin console, identify the application, client ID, publisher, requested scopes, and affected users or organizational units.
- Determine whether access is user-consented, administrator-approved, or both.
- Use the third-party app controls to restrict or remove the relevant grant, following Google Workspace’s app-access controls.
- Review OAuth token audit activity and sign-in events for the grant and the period immediately before revocation.
- Tell affected users which integrations were removed and what functionality will stop.
Google Workspace’s accessed-apps list can take up to 48 hours to reflect a token grant or revocation. Record when the change was made; a stale listing immediately after the change is not proof that revocation failed.
For integrations your organization still needs, narrow the allowed scopes or limit access to selected organizational units instead of leaving a broad tenant-wide grant in place.
Microsoft Entra work accounts: remove consent, assignments, and sessions
Microsoft Entra presents access through enterprise applications, OAuth consent grants, and application-role assignments. The correct action depends on whether one user consented or an administrator granted access for the tenant.
Inventory the enterprise application
- Identify the enterprise application and its application or client ID.
- Inspect delegated permissions, application permissions, user assignments, owners, and consent records.
- Check audit events for the consent grant, role assignment, sign-ins, and changes to credentials or owners.
- Use Microsoft’s application security operations guidance at Microsoft Entra security operations for applications to structure the review.
Revoke the appropriate grant
Remove the individual OAuth consent grant when access was limited to one user. Remove the application role assignment or tenant-wide consent when the application was approved for the organization. Microsoft’s guidance on detecting and remediating illicit consent grants explains the investigation and remediation path.
Rank #3
- NEVER FORGET A PASSWORD AGAIN: Almost every App. has a password, it is almost impossible to remember all the password log in details. This password book is specifically designed to help you create secure passwords and store all your passwords safely in one place. You will never forget your password log-in details again with this password keeper.
- ALPHABETICAL A-Z TABS FOR QUICK ACCESS: Alphabetical tabs design allows you to store your passwords alphabetically so you can find what you want faster, no more annoying searches!
- ANONYMOUS WITHOUT ANY TITLE: On the outside, this password notebook organizer looks just like those writing journals, there is no title listed on the cover, so no one would know it's a password book. But we still recommend keeping the internet password logbook in a safe place such as a locked drawer or a shelf full of books.
- THICK NO-BLEED PAPER: This 5.2" x 7.6" password book contains 74 sheets of thick 120gsm paper that resists ink smearing, say goodbye to those cheap password books that bleed ink!
- PREMIUM QUALITY & PERFECT MEDIUM SIZE: This password journal comes with a high-quality leatherette hardcover, an elastic band, pen holder, ribbon bookmarker, and inner accordion pocket. It measures 5.2 inches wide and 7.6 inches long, which is the perfect size for your needs.
For an active incident, disabling sign-in for the affected account can provide short-term containment, but it also interrupts the user’s normal work. Microsoft documents emergency access revocation at Revoke user access in an emergency in Microsoft Entra ID.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Account for token and session lag
Microsoft warns that already-issued access tokens may remain usable until their usual lifetime ends. Applications should stop accepting Entra access tokens after access is revoked, but an identity-provider change may not immediately close every app-controlled session. Ask the service owner to terminate active sessions, revoke refresh tokens where supported, and rotate application credentials if they were exposed.
Apple integrations: use the developer revocation path
Apple’s documented token-revocation endpoint is implementation guidance for developers rather than a universal consumer settings walkthrough. An integration can use a valid refresh or access token to invalidate the associated user authorization.
If you operate the integration, follow Apple’s token revocation documentation. For Sign in with Apple account deletion and token handling, see TN3194: Handling account deletions and revoking tokens for Sign in with Apple.
If you are the end user and cannot find a revocation control, contact the app developer or the organization administering the integration. Ask specifically whether they invalidated refresh tokens, closed app sessions, and deleted data already received.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Verify that revocation took effect
Do not treat a confirmation dialog as the end of the audit. Verification should test both future access and residual artifacts.
Run a controlled action test
- Ask the agent to perform the same low-risk action it previously performed, without exposing new sensitive data.
- Confirm that the provider or app returns an authorization error rather than completing the task.
- Check that no new message, file, event, purchase, or other side effect appears in the account.
A failed test demonstrates that the tested path is blocked; it does not prove that another credential or integration cannot reach the account.
Rank #4
- NEVER FORGET A PASSWORD AGAIN - Clever Fox password journal will help you create secure passwords and keep them safe and organized. This password book allows you to store all your passwords and other computer information in one place to find it easily.
- ALPHABETICAL A-Z TABS - Alphabetic tab system makes it easy to find any password you need. The book also has sections for most important passwords, wireless & email settings, software license information & additional notes.
- ELEGANT, SMART, PRACTICAL & SECURE PASSWORD ORGANIZATION - This password keeper book has been designed to be anonymous without an obvious title on the cover. For added security there is space to write hints instead of the password itself.
- POCKET SIZE & PREMIUM QUALITY - This internet address and password logbook with tabs comes in pocket size (4.0x5.5 inches). The password notebook has an eco-leahter hardcover, elastic band, pen loop, bookmark, pocket for notes, and thick 120gsm paper.
- 60-DAY MONEY-BACK GUARANTEE - We will exchange or refund your password organizer if you aren’t satisfied with your password organization for any reason. Reach out to us via message to refund your internet password logbook.
Check provider pages after their update window
Review the connected-app or enterprise-application page again. For Google Workspace, wait through the documented 48-hour accessed-apps update period before interpreting the list. Keep the timestamp, screenshots, and resulting status in the incident record.
Inspect the agent service
- Remove the integration from the agent’s own settings.
- Terminate active agent sessions and revoke refresh tokens if the service supports those controls.
- Review connected workspaces, webhooks, scheduled jobs, and alternate accounts.
- Delete stored credentials, exported tokens, or configuration files that are no longer needed.
Google recommends securely storing tokens and revoking or deleting them when they are no longer required. Its OAuth guidance is available at OAuth authorization best practices.
Understand what revocation does not erase
Revoking an authorization prevents future access through that authorization. It does not guarantee deletion of information already copied to the agent provider, app database, logs, backups, exports, or generated files.
Google explicitly warns that a third-party app may retain information it already received. Contact the developer and use its data-deletion, export, or account-closure process when you need past data removed. Ask what was stored, the retention period, backup treatment, and whether human support must complete the deletion.
Also check credentials the agent may have obtained outside the reviewed OAuth connection. A password, API key, browser cookie, downloaded file, or manually pasted secret can remain usable after an app grant is revoked. Rotate those credentials through the issuing service and invalidate active sessions where available.
If the connection was unauthorized, treat it as an incident
- Preserve the app identity, client ID, scopes, consenting user, grant time, audit records, and agent-run history.
- Revoke the user-level and, when appropriate, organization-level grants.
- Check for other applications, credentials, webhooks, or accounts used by the same agent.
- Review account activity for messages sent, files changed, events created, purchases made, or data exported.
- Terminate app-side sessions and rotate passwords, API keys, or other secrets that the agent could have seen.
- Request deletion of copied data from the third-party service.
- Escalate to the identity provider, workspace administrator, or agent vendor if you cannot establish that access ended.
Changing a password alone is not a substitute for revoking an OAuth or application grant. Provider-managed authorizations, refresh tokens, and app sessions are separate controls and must be checked independently.
Troubleshoot common failure modes
The agent still completes tasks
Look for a second authorization path: another app registration, a different user account, a tenant-wide grant, an API key, a browser session, or a service account. Compare the app or client ID in audit logs with the entry you revoked. Terminate the agent’s own session and rotate non-OAuth credentials.
Best Value
- Securely Remember All Your Passwords, Log-in's, User Names, ATM PIN Numbers and More
- Large Back-lit LCD Screen, QWERTY Keyboard - So Easy to Use
- Enter one PIN number and have access to 400 accounts. Search function included.
- Unit auto locks for 30 minutes after 5 consecutive incorrect PIN attempts
- Includes mini stylus for easier keypad entry
The app remains listed after removal
First distinguish a stale inventory page from an active grant. Google Workspace can take up to 48 hours to update its accessed-apps list. During that interval, rely on new authorization tests and audit events, then recheck after the provider’s update window.
You cannot find the agent by name
Search by publisher, app name, client ID, connected-app category, or the account the agent used. Providers often record the underlying application rather than the conversational agent label.
The organization removed a grant but one user still has access
Inspect both tenant-wide consent and individual delegated consent. Remove the remaining user grant, assignment, or session and verify the user’s app list after the provider’s normal propagation delay.
Recommended Free Tools
You need the app but not the agent
Use the agent-specific permission when the provider offers it, then review the app’s scopes and reduce them to the minimum required. Do not remove a shared app grant blindly if other approved workflows depend on it; document the narrower permission and test the affected workflow.
Make future agent access easier to audit
- Prefer integrations that show a distinct app identity, scopes, consent time, and revocation control.
- Grant the smallest practical scope and avoid account-management permissions for read-only tasks.
- Use separate accounts or projects for automation so a single agent cannot reach unrelated personal or production data.
- Record who approved each integration, why it is needed, and its owner.
- Set a review date for long-lived connections and remove unused grants.
- Store tokens securely, never paste them into prompts or shared documents, and delete them when the integration is retired.
- For work tenants, monitor consent, application-role assignments, sign-ins, and token activity centrally.
- Document the provider-specific revocation path before enabling an agent, including how to terminate app-side sessions and request data deletion.
For native applications and other OAuth implementations, Google’s implementation guidance covers secure authorization patterns and token handling at OAuth 2.0 for iOS and desktop apps.
The Bottom Line
To close an AI agent’s access reliably, revoke the agent permission, remove the underlying app or tenant grant when required, terminate residual sessions and tokens, investigate audit history, and separately request deletion of data the service already copied.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
