# Government IT Teams Tighten MCP Controls

A Cloud Security Alliance research note finds that pinning an MCP server’s top-level version does not lock its transitive dependencies, so code may change when an environment is rebuilt. For government and contractor IT teams, this creates a software-supply-chain risk in coding-assistant environments and makes reproducible dependency management relevant to system approval and contractor technical baselines.

- Teams should inventory MCP launch configurations and require exact versions and reproducible, locked artifacts for approved servers.
- Release-age delays, script restrictions, and a tested update process are among the controls identified in the note.
- Procurement professionals can incorporate these controls into technical requirements and assessments for MCP-enabled tools and contractor environments. The signal identifies no specific solicitation, award, contract value, or deadline.

**Jurisdictions:** federal
**Industries:** Information Technology
**Topics:** Cybersecurity
**Published:** November 15, 2026

### Government Entities
- Cybersecurity and Infrastructure Security Agency (CISA)
- National Institute of Standards and Technology (NIST)

### Sources
- [Pinned but Not Frozen: Dependency Drift in Coding-Assistant MCP Servers – Lab Space](https://labs.cloudsecurityalliance.org/research/csa-research-note-mcp-server-dependency-drift-20261115-csa-s) - Cloud Security Alliance (CSA)