Aller au contenu
Implementa.
← Full glossary

Agent supply chain

security

agent software supply chain · skill supply chain · agent supply-chain risk

Every piece of third-party software your agent loads to get work done: skills, plug-ins, MCP servers, add-ons and connectors. You didn't write it, nobody signed it, and it runs with your agent's permissions.

For twenty years the industry learned to sign the code that lands on a machine: drivers, packages, dependencies. With agents we started from scratch. A skill installs in one click, ships instructions and sometimes code, and inherits whatever the loading agent can reach: your CRM, your inbox, your file store. The agent supply chain is the inventory almost no company has written down. There is exactly one public number in this space, and it deserves to be quoted for what it is: security vendor AIR says it filters out roughly 27% of the public skills and add-ons it encounters using its own allowlist (TechCrunch, 2026-09-01). That is their filter, not a measurement of anyone's installed base. Operationally it comes down to three questions: which skills, plug-ins and MCP servers each agent has connected; who approved them; and what happens the day one of them changes owner or behaviour.

How it differs from

Software bill of materials (SBOM)
An SBOM inventories the dependencies of an application you compile and ship. Here the component is loaded by the agent at run time, often without ever touching your pipeline.
Shadow AI
Shadow AI is people using unapproved AI tools. Here the one installing unvetted software is the agent.

Examples

  • A support agent that loads a public billing skill pulled from a marketplace and can read every customer ticket.
  • An MCP server a team stood up to wire the agent into the ERP, with no security review and no named owner.

FAQ

What exactly counts as an agent's supply chain?
Skills and capability packs, plug-ins, MCP servers, system connectors, external tools the agent can invoke, and the models underneath. Everything the agent executes that your team didn't write.
Where do you start controlling it?
With the list. Before you buy a product, write down which skills, plug-ins and MCP servers each production agent has connected, who approved them and what systems they reach. Most companies discover in that exercise that nobody owns it.

Related terms

Sources & further reading