This website counts page views with Cloudflare Web Analytics, which sets no cookies and stores nothing on your device. If you choose Allow, embedded content such as Spotify podcast players also sets optional cookies. Choose Deny to turn off both. Cookie Notice
Each team installs its own agents and copies skills and connectors from public marketplaces, and nobody chose most of them.
Sales uses the Claude desktop app, engineering uses three coding agents, and someone in finance found a connector on a public marketplace. Each one can read files, run commands, or reach company data with its user's access. The more of them there are, the more there is to review, patch, and explain after an incident.
Research from across the industry shows how much of it nobody chose.
66%
of office professionals have used AI tools at work that they believed company policy didn't allow.
Survey of 1,250 professionals at companies with $500 million or more in revenue, in the US, UK, Australia, and Japan.
An approved list needs a way to see who uses something else.
Control Plane lists every agent, skill, plugin, connector, and identity on every device, so you start from what teams actually use.
Approved set
Trust what you support
Mark the agents, skills, and connectors you support as trusted, or trust a publisher to approve its future versions too.
Exceptions
See who uses something else
Filter Control Plane to anything outside the approved set and see which devices and teams use it, so you can move them over or add it to the list.
Enforcement
Block what you've ruled out
Block the skills and plugins you've decided against, and they stop loading on every device.
Where teams start
Four ways to shrink it.
Pick the one that matches the problem in front of you, then add the others.
Approved tools
Standardize on approved AI tools
Choose the agents the company supports, see which devices run anything else, and move those teams over.
Skill library
Build an approved skill library
Trust the skills and connectors teams rely on, so they pick from a reviewed list instead of public marketplaces.
Unused components
Remove what nobody uses
Find skills, plugins, and connectors installed on a handful of devices and never trusted, and block or remove them.
Identities
Cut access agents don't need
See which identities each agent can reach, and move agents off borrowed personal accounts and shared cloud profiles.
How it works
Start from what teams use, then narrow it down.
01 · Supply ChainSee what's installed
Push one package through your device management tool, such as Jamf, Iru, or Intune.
02 · Supply ChainChoose the approved set
Trust the agents, skills, and connectors you'll support, and agree the list with each team.
03 · Supply ChainShrink the rest
Work through the exceptions team by team, then block the skills and plugins nobody should use. New components start unreviewed, so the list stays short.
Example deployment
Where an approved list starts.
Illustrative example
A 140-person software company with one IT lead.
This company is fictional. The numbers come from a modelled fleet, not a customer.
Claude on 61 of 140 devices, 27 of them outside engineering
230 skills found in the first full inventory, 14 of them unknown
2 skills matched a critical rule and were blocked
What it costs
Priced per device. Always predictable.
Supply Chain is priced per device, 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.
Reduce agent risk without slowing your teams down.
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.