Part 7 · Agentic AI Security
ASI04: Agentic Supply Chain Vulnerabilities
Agents load tools, prompts, and other agents at run time, so a compromised component can enter while the system is live.
What it is
Agentic supply chain vulnerabilities arise when agents, tools, or related artifacts come from third parties and may be malicious, compromised, or tampered with. These components include models, tools, plug-ins, datasets, other agents, MCP and A2A interfaces, registries, and update channels.
Unlike a traditional dependency, many of these components are discovered and loaded dynamically.
How the attack unfolds
A rug pull: a component earns trust, then changes after it has been adopted.
Real-world case
In September 2025, Koi Security reported postmark-mcp, described as the first malicious MCP server found in the wild. After 15 clean releases, a new version quietly added a hidden BCC to outgoing emails.
Defenses
- Verify provenance. Sign and attest tools, prompts, and agent components.
- Maintain inventories. Keep SBOMs and AI bills of materials current.
- Pin versions. Review changes before accepting an update.
- Use curated registries. Block untrusted sources.
- Sandbox components. Limit each tool's network and data access.
- Have a kill switch. Be able to revoke a compromised component quickly.
Common misconception
"We reviewed that tool when we installed it."
Remote tools and updates can change after review, so trust must be checked continuously.
Key takeaways
- Agents depend on tools, servers, prompts, and other agents.
- Trusted components can change after review.
- Pin, verify, and sandbox what agents load.