Inspection is not a shield — Tenable and OpenAI vet the agent marketplace, and Article 25(4) exempts the suppliers

A vendor security review for community-built agent components is evidence, not a liability boundary. AI Act Article 25(1)(a) makes whoever puts their name on a high-risk system the provider; Article 25(4) gives that provider one instrument for third-party components — a written agreement with the supplier — and its second sentence exempts anyone distributing under a free and open-source licence. The Tenable CyberAgents Exchange is free and open source, so the badge arrives and the counterparty does not.

Post

A security vendor just announced a review process for community-built AI agents. It does not move your liability by one metre.

On 3 September 2026 Tenable and OpenAI announced the CyberAgents Exchange AI Inspector: a security review for community-contributed agents, skills, MCP servers and multi-agent playbooks, combining OpenAI's cyber models with Tenable One AI Exposure and Tenable's own researchers. The exchange itself opened on 4 August with more than 50 components. A month later it lists more than 100. The Inspector is expected this month.

Good thing. Also being read wrong.

If you pull a component off a public exchange into a system that sits on an Annex III path, here is what the AI Act actually says:

Article 25(1)(a): put your name or trademark on a high-risk system already on the market and you are the provider, carrying the full Article 16 obligation set. A vendor's review badge is not your name coming off.
Article 25(4): the Act's one instrument for third-party components is a written agreement with the supplier, specifying the information, capabilities and technical access you need in order to comply.
Article 25(4), second sentence: that paragraph "shall not apply to third parties making accessible to the public tools, services, processes, or components, other than general-purpose AI models, under a free and open-source licence."

The exchange is free and open source. That is the point of it. It also means there is no counterparty to bind. The obligation does not vanish. It lands entirely on you.

What I would do Monday:

Pin the commit, not the listing. A marketplace entry is mutable. Your evidence has to be immutable.
File the inspection report as dated evidence in your Article 9 risk file. It is evidence, not a supplier warranty.
For anything on an Annex III path, prefer a supplier you can actually sign with. Annex III high-risk applies from 2 December 2027, which is close enough to start choosing now.

An inspection is evidence. A licence is a liability boundary. This week only the first one moved.

Which of the two are you actually relying on?

#EUAIAct #AgenticAI #MCP #AICompliance #SoftwareSupplyChain

AI disclosure: the narration voice, the cover art and the brand ident animation in this video are AI-generated. The script, the claims and the source checks are mine.

First comment

Sources.

Tenable and OpenAI announce the CyberAgents Exchange AI Inspector, 3 September 2026 — the primary release, with the component types and the September availability. https://www.tenable.com/press-releases/tenable-uses-openai-gpt-cyber-models-to-help-defenders-inspect-community-built-ai-components

Same release on the wire, timestamped 3 September 2026 17:57 ET — useful because most coverage is dated the 4th. https://www.globenewswire.com/news-release/2026/09/03/3356323/0/en/tenable-uses-openai-gpt-cyber-models-to-help-defenders-inspect-community-built-ai-components.html

The exchange's own launch release, 4 August 2026 — free, open source, more than 50 components at launch. https://www.tenable.com/press-releases/tenable-launches-industrys-first-open-source-ai-agent-exchange

The components themselves, so you can pin a commit rather than a listing. https://github.com/tenable/cyberagents-exchange

AI Act Article 25, responsibilities along the AI value chain — the European Commission's own text, including the open-source carve-out in 25(4). https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-25

One point cut for length: Article 25(2) says the initial provider stops being the provider once you take that role, and must hand you technical documentation, known limitations and failure modes, and targeted technical access. That is the cooperation duty you lose along with the counterparty when the component arrives under an open-source licence — nobody upstream owes you the failure modes.

AI disclosure: the narration voice, the cover art and the brand ident animation in this video are AI-generated. The script, the claims and the source checks are mine.

Claims

Sources

Corrections

Aggregator listings date the Tenable/OpenAI announcement 4 September 2026. The release itself and the wire timestamp are 3 September 2026, 17:57 ET. The edition uses 3 September throughout.

AI disclosure

The video for this edition contains AI-generated media: the narration is a synthetic voice, and the cover art and the brand ident animation are generated. The script, the claims and the source verification are human-authored and human-checked. Assets carry IPTC DigitalSourceType and C2PA Content Credentials.

Inspection is not a shield — Tenable and OpenAI vet the agent marketplace, and Article 25(4) exempts the suppliers

A vendor security review for community-built agent components is evidence, not a liability boundary. AI Act Article 25(1)(a) makes whoever puts their name on a high-risk system the provider; Article 25(4) gives that provider one instrument for third-party components — a written agreement with the supplier — and its second sentence exempts anyone distributing under a free and open-source licence. The Tenable CyberAgents Exchange is free and open source, so the badge arrives and the counterparty does not.

Post

A security vendor just announced a review process for community-built AI agents. It does not move your liability by one metre.

Good thing. Also being read wrong.

If you pull a component off a public exchange into a system that sits on an Annex III path, here is what the AI Act actually says:

Article 25(1)(a): put your name or trademark on a high-risk system already on the market and you are the provider, carrying the full Article 16 obligation set. A vendor's review badge is not your name coming off.

Article 25(4): the Act's one instrument for third-party components is a written agreement with the supplier, specifying the information, capabilities and technical access you need in order to comply.

Article 25(4), second sentence: that paragraph "shall not apply to third parties making accessible to the public tools, services, processes, or components, other than general-purpose AI models, under a free and open-source licence."

The exchange is free and open source. That is the point of it. It also means there is no counterparty to bind. The obligation does not vanish. It lands entirely on you.

What I would do Monday:

Pin the commit, not the listing. A marketplace entry is mutable. Your evidence has to be immutable.

File the inspection report as dated evidence in your Article 9 risk file. It is evidence, not a supplier warranty.

For anything on an Annex III path, prefer a supplier you can actually sign with. Annex III high-risk applies from 2 December 2027, which is close enough to start choosing now.

An inspection is evidence. A licence is a liability boundary. This week only the first one moved.

Which of the two are you actually relying on?

#EUAIAct #AgenticAI #MCP #AICompliance #SoftwareSupplyChain

AI disclosure: the narration voice, the cover art and the brand ident animation in this video are AI-generated. The script, the claims and the source checks are mine.

AI disclosure