Solutions · By risk
Supply Chain maps which identities each AI agent can use or inherit, from GitHub accounts to SSH keys, without reading any secret.
device:endpoint_4c19 trust:any⌘↵New agent found · Unreviewed
Critical finding · Blocked · Applied
Identified · Trusted
The problem
An agent can use the accounts its user is signed in to, and nobody has a list of which agent can reach which identity.
Agents are set up with accounts for GitHub, cloud providers, and business apps. They also inherit what the environment they run in can reach: AWS and Google Cloud profiles, Kubernetes contexts, and SSH keys loaded for the session. Identity tools see the account, and device tools see the app. Neither shows which agent can use which identity.
Research from across the industry shows how much access already sits where agents can reach it.
unique secrets exposed in MCP-related configuration files on public GitHub.
2,117 of them were valid credentials, from GitGuardian's scan of public GitHub in 2025.
The files that connect agents to tools often hold live credentials.
GitGuardian, State of Secrets Sprawl 2026, March 2026
unique, verified secrets leaked in the s1ngularity attack, which told local AI command line tools to search for credentials.
Over 1,700 users had secrets leaked; about half of all victims had at least one AI command line tool installed.
Whatever identities an agent can reach, an attacker can reach through it.
Wiz, September 2025
What changes
Control Plane lists each agent on each device with the identities it's configured to use or may inherit, such as GitHub accounts, cloud profiles, Kubernetes contexts, and SSH keys, and how each one is reached.
Each link says whether the agent is configured with an identity, references a credential source, or has local evidence that the source exists, so nobody reads more into it than the device shows.
Supply Chain flags credentials written into configuration files, a person's own account used by an agent, shared profiles, and cloud access an agent inherits without anyone choosing it.
Supply Chain builds the map from account names and non-secret metadata only. Passwords, tokens, private keys, browser sessions, and vault contents are never read.
How it works
Push one package through your device management tool, such as Jamf, Iru, or Intune. Identity discovery runs in the same scan as the agent inventory.
Select a device or agent in Control Plane and see each identity it can reach, how, and how strong the evidence is.
Move agents to their own managed identities where Control Plane recommends it, and add Runtime to check what agents do with the access they have.
Engineering · 1 device · identitiesHuman account · identity-7f3a
Provider profile · references a credential source
Public key metadata only
Recommended: a managed identity for the agent
In Control Plane
Open any agent to see its identities, written plainly.
What it costs
Supply Chain and Runtime are priced per device, alone or together, with free devices on every plan. Your bill depends on how many devices you cover, so heavier agent use doesn't change it, and finance can plan ahead.
Questions
Your secrets stay where they are. Supply Chain maps access from account names, profile names, and other non-secret metadata, and never reads passwords, tokens, private keys, browser sessions, or password manager vaults.
Only the people who need them: workspace owners and administrators. Everyone else sees a stand-in name for each identity, and every reveal of an exact name is recorded.
Agent and connector configuration, plus developer identity sources such as GitHub CLI accounts, AWS, Google Cloud, and Azure profiles, Kubernetes contexts, and SSH agent keys.
Yes. Identity discovery is part of Supply Chain and runs in the same package and scan as the agent inventory.
Modules used
device:endpoint_4c19 trust:any⌘↵New agent found · Unreviewed
Critical finding · Blocked · Applied
Identified · Trusted
Supply Chain
See which AI agents run on each device and which identities they can reach, check the skills they load, and block what you don't trust.
Explore Supply ChainRun the setup steps from the README
Bash curl -s https://get.example.dev/setup.sh | bash
Blocked by Signals Corps Runtime
I didn't run it. Signals Corps blocks piping a remote script into the shell. I can download it so we can read it first.
Runtime
Stop unsafe agent actions in real time while safe work carries on.
Explore RuntimeEarly access
Start reducing agent risk before general release by checking agent components, controlling agent actions, and hunting through your AI security logs. Signals Corps Control Plane opens to early sign ups in the next few weeks, so join the waitlist with your company email.