Topic starter
18/08/2026 2:09 pm
TL;DR: AI supply chain security now includes models, agents, MCP servers, skill files, and prompt-driven configuration, according to Xygeni, because hidden instructions and unreviewed integrations can alter what assistants can do and reach. Conventional AppSec and endpoint tools miss this layer, so inventory, detection, and enforcement need to move together.
Editorial analysis by NHI Mgmt Group, based on content published by Xygeni: “AI Security: The Files Nobody Reviews Are Now Your Biggest Attack Surface”.
Key questions
Q: What breaks when AI assistants can read unreviewed skill files or MCP configs?
A: The trust model breaks because the assistant may treat plain text instructions as authoritative policy and then invoke tools, endpoints or data sources that no reviewer intended.
Q: When do AI supply chain risks become a governance problem rather than a data science issue?
A: They become a governance problem as soon as a model depends on external data, embedded components, hosted infrastructure, or supplier-operated services.
Q: How should security teams control assistant access to tools and data?
A: Teams should set explicit allowlists for tools, endpoints and data sources, then review every AI artefact that can influence execution.
Practitioner guidance
- Inventory all AI artefacts as governed assets Map models, agents, prompts, skills, rules files and MCP servers to owners, approvals and runtime reach so the team can answer what exists and who controls it.
- Review instruction files with change control Require code-review style approval for skill files, rules files and MCP descriptions because plain text can still alter assistant behaviour and tool access.
- Constrain assistant tool reach with allowlists Limit which tools, endpoints and data sources an assistant can invoke, and block unapproved MCP servers or connectors before they execute.
Bottom line: AI supply chain security now extends to instruction files, connectors and agent configs, which means the control problem reaches well beyond conventional code scanning.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
18/08/2026 3:02 pm
AI supply chain security has become an identity governance problem, not just an AppSec problem. Once models, agents, MCP servers and skill files can influence execution, the question is no longer only whether code is safe. It is also which non-human actors are authorised to invoke which tools, under what conditions, and with what review path. That makes the trust boundary around AI systems a governance object in its own right, not an implementation detail.
A few things that frame the scale:
- Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.
A question worth separating out:
Q: What should organisations do first to govern AI supply chain risk?
A: Start by building an AI inventory that lists models, agents, prompts, skills, MCP servers and the dependencies around them. Once that map exists, attach ownership, approval status and runtime reach so risk can be triaged, audited and enforced instead of guessed at from code alone.
👉 Read our full editorial: AI supply chain security now spans models, MCP servers and skills