Recommended Free Tools
To audit and restrict an AI agent’s credentials, inventory its identity and every access path, calculate what it can do across tools and downstream services, then enforce task-specific authorization before each action. Give each agent a distinct, owned identity; prefer short-lived or federated access; log decisions without logging secrets; and test that revocation actually cuts off the whole call chain.
What credentials can this AI agent access?
Start with the agent’s effective access, not just a list of passwords or a single role document. An agent may act through a workload identity, service principal, delegated token, stored secret, tool permission, or a downstream integration. Individually narrow grants can combine into broad end-to-end capability. Microsoft’s least-privilege guidance for agent identities recommends reviewing aggregate permissions across agents and tools.
As an Amazon Associate I earn from qualifying purchases.
Build an inventory of identities and access paths
For each deployed or planned agent, record its owner, purpose, environment, identity provider, identity type, credential source, approved tools, and downstream resources. Include delegated token flows and integrations that obtain access on the agent’s behalf. For every path, note the resources and actions it enables, the policy or role that allows them, and how the access is revoked.
Give each agent a distinct identity with a named human owner and documented purpose. A shared credential makes it harder to tell which agent acted and harder to contain a compromise. Keep machine identity separate from the human requester: where delegated actions are supported, carry explicit user context through the call chain rather than silently using a shared human credential. AWS describes clear agent-versus-human permission separation and attributable actions as desired outcomes in its Agentic AI Lens.
#1 Best Overall
- POWERFUL SECURITY KEY: The Security Key C NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key C NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key C NFC via USB-C and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
Map the complete authorization chain
Trace an example action from the agent through its orchestrator, tool, API, and downstream service. At each boundary, identify which identity is presented, which scope or role is checked, and what resource and action are allowed. Record the combined result, not simply the permissions visible in one console. An agent with read access to a tool that can invoke a broadly privileged integration may have more effective access than its own role suggests.
How do I limit an AI agent’s permissions?
Define what each workflow needs before assigning access. Match permissions to the task, resource, and action, and enforce those limits in trusted application code or a policy layer before execution. The model can propose an action; it must not be the authority that decides whether the action is permitted. The tool and downstream service should also enforce their own authorization boundaries.
Rank #2
- POWERFUL SECURITY KEY: The YubiKey 5C NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5C NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5C NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
Create a task-to-permission matrix
For each workflow, list the data it must access, the actions it must perform, and the tools it requires. Map those requirements to the narrowest available identity role, API scope, resource permission, and tool authorization. Separate read and write access where practical. Remove unused tools and deny unreviewed integrations by default. Recheck the aggregate result after combining grants.
| Workflow need | Permission design | Execution check |
|---|---|---|
| Read a defined set of records | Limit the identity and tool to the required resources and read operations. | Verify the resource and requested operation before the tool call. |
| Update a record or submit a change | Grant write access only to the relevant resource and workflow. | Check the specific change against policy; require approval if its impact warrants it. |
| Use an external integration | Allow only a reviewed tool and its required downstream scope. | Authorize at the tool boundary and let the downstream service enforce its own access rules. |
These are design patterns, not product-specific role names: the exact controls depend on the identity provider, tool, and downstream service. OWASP’s guidance on excessive agency recommends least privilege, per-tool scoping, explicit authorization for sensitive operations, and human oversight for high-risk actions.
Rank #3
- POWERFUL SECURITY KEY: The YubiKey 5 NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5 NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5 NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
Gate high-impact actions separately
Classify actions by their consequences. Deletion, external publication, data export, privilege changes, and financial or administrative operations may need independent validation, explicit human approval, or just-in-time elevation. Apply the check to the requested action and target resource, not only to the agent’s general identity. A broad identity grant should not silently make every tool action acceptable.
How should credentials be stored and kept short-lived?
Prefer platform-managed identity, federation, or short-lived tokens where supported. If a workflow requires a static secret, place it in an access-controlled secrets manager, retrieve it at runtime, and define rotation and emergency revocation. Do not put secrets in source code, prompts, or plaintext logs. AWS recommends retrieving client credentials from Secrets Manager rather than keeping them in code or environment variables in its workload secrets guidance.
Rank #4
- POWERFUL SECURITY KEY: The Security Key NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key NFC via USB-A and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
AWS’s Agentic AI Lens gives an AWS-specific example of temporary STS role credentials with session policies and short durations of 15 to 60 minutes. That is an implementation example, not a universal standard or a duration suitable for every workflow. Choose credential lifetime and any elevation window according to task, risk, and platform behavior. Microsoft’s third-party agent integration guidance describes on-demand token acquisition without direct credential handling by the third-party agent.
Free tools Windows power users keep installed
One-click scans. No signup required.
How do I audit what an AI agent did?
For consequential actions, keep structured records that let an operator reconstruct the decision and its execution. Capture the agent identity, any delegated human context, tool and scope, action, target resource, authorization result, approval context, execution result, and a correlation identifier. Use correlation data to connect the orchestrator event to tool and downstream service records.
Best Value
- POWERFUL SECURITY KEY: The YubiKey 5 is a versatile physical passkey that protects your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5 secures 100+ of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5 via USB and tap it to authenticate. No batteries, no internet connection, and no extra fees required.
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
Do not record raw tokens, passwords, or secret values. Protect audit records because they can still contain sensitive business or personal information. OWASP recommends structured audit metadata and warns against unrestricted tools and plaintext credential logging in its excessive-agency guidance. Microsoft’s agent least-privilege pattern also calls for detailed action logging.
How do I test revocation and catch permission drift?
Rehearse containment with the actual agent, tools, and downstream services. Disabling an identity or revoking a token may not immediately invalidate every existing session or integration, so verify the behavior rather than assuming that one control cuts off the entire chain.
- Disable the agent identity using the mechanism for your identity provider.
- Revoke or allow relevant tokens to expire, and rotate any secret that may have been exposed.
- Remove stale grants from tools and downstream resources where necessary.
- Attempt the agent’s previously permitted calls and confirm that each relevant service rejects access.
- Record the observed revocation behavior and update the response procedure if any path remains usable.
Repeat the effective-access review when a workflow, tool, data scope, or deployment environment changes. AWS identifies permission drift and weak review cadence as risks in its Agentic AI Lens; Microsoft recommends revocation testing and review after material changes in its least-privilege guidance.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhat to compare when choosing an identity or secrets implementation
Evaluate implementations against the same control questions rather than comparing product labels alone. Verify how each integration actually handles token scope, downstream authorization, audit fields, and revocation in your deployment.
Quick Recap
- Identity separation: Can each agent have a distinct identity and named owner, separate from human accounts?
- Scope granularity: Can permissions be restricted by resource, API, site, action, and task, with downstream enforcement?
- Lifetime and delegation: Are managed identities, federation, short-lived tokens, and explicit user delegation supported?
- Secret controls: Can unavoidable secrets be constrained, retrieved at runtime, rotated, and revoked?
- Auditability: Can records show actor, authority, scope, action, resource, decision, approval, and correlation context without secret values?
- Containment: Can operators disable an agent and invalidate access across its tool chain, and can they demonstrate that with a test?
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.
