2. Supply Chain & Extensibility

How to govern connectors, MCP servers, plugins, skills, extensions, hooks, and agent frameworks as a software supply chain with real attack surface.

Last reviewed: August 18, 2026

Every connector, MCP server, plugin, skill, and hook is a software dependency with real attack surface. Treat the AI extension ecosystem the same way you treat third-party code — with intake, review, allowlisting, and owner accountability.

Articles in this section

1. 2.1 Connectors and apps: the integration backbone
2. 2.2 MCP servers: securing the protocol
3. 2.3 MCP gateways and allowlisting
4. 2.4 Analyzing skills for risk
5. 2.5 Plugins and marketplaces
6. 2.6 AI hooks: inference controls and lifecycle automation
7. 2.7 The supply-chain review workflow
8. 2.8 Signing and packaging
9. 2.9 SaaS agent-building supply-chain
10. 2.10 Hosted-agent framework dependencies

Frequently asked questions

What belongs in the AI supply-chain register? Record every connector, MCP server, skill, plugin, hook, model, SDK, container, template, and agent framework with its owner, source, version, permissions, data reach, review date, and update trigger. Include components supplied through marketplaces and repositories.

When must an extension be reviewed again? Review after a material permission, owner, source, version, signing, tool, dependency, or update-channel change. Re-run the review after incidents and when a component begins handling a new data class or production action.

Related handbook guidance

• AI Security Handbook
• 5.3 Supply chain attacks and notable CVEs
• 7.4 The vendor-neutral control matrix
• Security Team Checklist