In introducing the American Security Robotics Act of 2026, Senators Tom Cotton (R-AR) and Chuck Schumer (D-NY) have extended a now familiar congressional playbook into a new and consequential domain: robotics. The bill would prohibit executive agencies from procuring or operating unmanned ground vehicle systems (UGVs) manufactured or assembled by “covered foreign entities,” a term that targets companies tied to adversarial nations such as China.
The legislation also reflects early signs of bicameral alignment. Representative Elise Stefanik (R-NY-21) has introduced companion legislation in the House, signaling that concerns regarding robotics systems manufactured by certain foreign entities are not confined to a single chamber or party.
At one level, the proposal is straightforward. At another, it reflects a maturing legislative architecture that has evolved across successive National Defense Authorization Acts (NDAAs) and related statutes—an architecture that is increasingly product-specific, attentive to supply chain risk, and focused on issues of data access, operational control, and systemic vulnerability.
From Networks to Nodes to Machines
Congress’s earliest modern forays into technology-focused procurement prohibitions—most notably Section 889 of the FY 2019 NDAA—focused on telecommunications infrastructure. Section 889 prohibited the federal government from procuring or using certain telecommunications equipment and services from named Chinese companies and, critically, extended that prohibition to contractors that use such equipment anywhere in their systems.
Section 889 reflected concerns about network infiltration—the risk that adversarial telecommunications infrastructure could permit data exfiltration and enable persistent surveillance or operational disruption.
Subsequent provisions expanded in both scope and sophistication. Section 5949 of the FY 2023 NDAA, for example, shifted focus to semiconductors and microelectronics targeting a different layer of the technology stack while reflecting the same core concern: supply chain dependency, particularly control over the sourcing of key inputs to advanced computing systems, as a national security risk.
The American Security Robotics Act represents the next logical step. It shifts the focus from infrastructure and components to autonomous, data-generating, physically active systems. These are not passive nodes in a network; they are actors in the physical world—robots capable of movement, sensing, and in some cases, decisionmaking.
Core Prohibitions: A Familiar Structure, Applied to a New Domain
The bill adopts a structure that will be immediately recognizable to practitioners familiar with Section 889 and its progeny.
First, the statutory definition is precise in design, but broad in reach. In traditional defense parlance, a UGV refers to a ground-based robotic platform: typically, bomb disposal robots and small tracked reconnaissance systems. The Act’s scope is more expansive, however. It encompasses any mechanical device capable of locomotion on the ground, whether remotely operated or autonomous, and expressly includes remote surveillance vehicles, autonomous patrol technologies, “mobile robotics,” and even humanoid robots. Yet the result is not a vague or overinclusive category, but a deliberately constructed legislative umbrella designed to capture a wide and evolving segment of modern robotics.
Further, the definition is explicitly systems‑oriented. A “covered unmanned ground vehicle system” encompasses not only the robotic platform itself, but also its payload and any external control devices. This reflects an understanding that risk does not reside solely in the robot’s physical chassis, but in the broader ecosystem of sensors, controllers, and data pathways that enable its operation—and that make these systems both valuable and potentially vulnerable to adversarial control or exploitation.
Second, it establishes a three-part prohibition:
- A ban on procurement of covered systems;
- A ban on the operation of such systems, taking effect one year after enactment; and
- A funding restriction preventing the use of federal funds—whether through contracts, grants, or cooperative agreements—to procure or operate them.
Third, the Act extends its reach to contracted services, ensuring that agencies cannot circumvent the prohibition by outsourcing robotic capabilities.
Key Distinction: The Physicality of Risk
What distinguishes the Robotics Act from earlier prohibitions is the physical dimension of the risk it addresses.
Telecommunications equipment and semiconductors raise concerns about data exfiltration and system integrity. Robotics raises those concerns—but adds another layer: kinetic consequence.
An unmanned ground vehicle deployed by a federal agency—whether for law enforcement, infrastructure inspection, or logistics—does not merely process data. It acts in the physical world. If compromised by an adversary, it could be redirected, disabled, or manipulated in ways that have immediate and tangible consequences.
Congress appears to be responding to this shift by treating robotics not simply as another IT category, but as a hybrid domain—one that combines software‑enabled vulnerabilities with real world operational and physical risk.
Exemptions: Narrow and Operationally Driven
Like its predecessors, the bill includes exemptions—but they are carefully cabined.
Agencies such as the Departments of War, Homeland Security, Justice, and State may procure or operate covered robotics systems for specified purposes, including testing, evaluation, counterintelligence, and law enforcement activities. Alternatively, an exemption may apply where the system has been modified such that it can no longer transfer data to or download data from a covered foreign entity and poses no cybersecurity risk.
These exemptions reflect two realities. First, exposure is sometimes necessary to counter risk; agencies must be able to study adversary systems and develop countermeasures. Second, Congress is increasingly willing to allow risk mitigation through technical controls, provided those controls are deemed sufficient through an agency head‑level determination.
Executive Branch Alignment: Robotics as Industrial Policy
The Robotics Act also arrives at a moment when the Trump Administration has begun to treat robotics not merely as a niche capability, but as a core element of industrial policy and national security competition. Recent Department of War initiatives—particularly those focused on autonomous, AI‑enabled systems operating across multiple domains—reflect a concerted push to accelerate domestic robotics innovation and deployment.
In that context, the Cotton–Schumer proposal can be understood as the supply side complement to an increasingly assertive demand signal. While the Administration works to expand U.S. capacity and adoption of advanced robotics, Congress is moving to exclude adversary-linked platforms from the federal ecosystem altogether. The two approaches are mutually reinforcing. By narrowing the field of eligible suppliers, Congress effectively channels federal demand toward trusted or domestic providers, amplifying industrial base objectives. At the same time, this alignment may create near-term friction—particularly for research institutions and agencies that have relied on lower cost foreign platforms—but, over time, it is likely to accelerate the development of a more secure and self sufficient U.S. robotics sector.
At the same time, these restrictions will operate within a broader foreign policy context in which the Executive Branch may seek to stabilize bilateral engagement with China. Measures that further narrow market access for Chinese‑manufactured technologies can complicate diplomatic signaling and invite reciprocal responses, even where the underlying national security rationale is compelling. Accordingly, the bill’s practical effect may depend as much on coordinated implementation and clear messaging as on the formal scope of the prohibition—ensuring that risk‑based protections for sensitive systems are understood as targeted safeguards rather than a general escalation in economic confrontation.
A Likely Vehicle: The FY 2027 NDAA
If history is a guide, this measure is far more likely to be enacted as part of a broader legislative package than as a standalone bill. The NDAA for FY 2027 presents the most plausible vehicle for enactment. Congress has repeatedly used the NDAA to advance product-specific procurement bans—including Section 889 and subsequent Section 5949 semiconductor and supply chain restrictions. The NDAA’s near guaranteed annual passage provides a reliable pathway for bipartisan measures that might otherwise struggle to advance independently.
As a threshold matter, a provision limited in application to the Department of War would fall squarely within the core jurisdiction of the Armed Services Committees. Framed in that manner, the subject matter would align cleanly with the NDAA’s traditional focus on defense organization, capabilities, and risk management within the defense enterprise.
Even were the prohibition to retain its current, Executive Branch‑wide application, it would not necessarily fall outside the permissible scope of the NDAA. Where such a provision is introduced after the NDAA is reported to the floor, and where the committees of jurisdiction outside Armed Services concur, the measure remains procedurally viable as part of the NDAA package, rather than requiring freestanding authorization.
Moreover, the NDAA conference process offers a structured forum to refine the bill and integrate it into a broader strategic framework addressing autonomy, artificial intelligence, and supply chain security. Particularly if the Administration continues to elevate robotics as a national priority, this provision could emerge in conference not merely as a restriction, but as part of a comprehensive legislative approach to robotics and autonomous systems.
A Broader Legislative Trend: Toward Product-Specific Decoupling
Taken together with Section 889, Section 5949, and related provisions—including those tied to the Section 1260H list and associated procurement restrictions—the Robotics Act reinforces a broader trend: the gradual construction of a product-specific decoupling regime.
Rather than imposing sweeping, economy-wide restrictions, Congress has opted for a targeted approach, identifying specific categories of technology and imposing tailored prohibitions that reflect their unique risk profiles. This approach allows for iterative policymaking and facilitates bipartisan consensus, but it also creates an increasingly complex compliance environment for federal agencies and contractors alike.
Implications for Government and Industry
For agencies, implementation will require inventory, assessment, and transition planning. The one‑year delay on the prohibition on operating such systems provides some runway, but experience suggests that compliance will demand significant effort and coordination.
For contractors, the Robotics Act—if enacted—would likely have implications extending beyond federal procurement. The combination of procurement bans and funding restrictions could create de facto market barriers, particularly for firms reliant on federal customers or federally funded research.
More broadly, the Act signals where Congress is headed. Robotics is unlikely to be the final frontier. As emerging technologies continue to blur the boundary between digital and physical systems, Congress appears poised to extend this model further.