US–Iran Foreign Policy Explained: How Presidential War Powers on Iran Actually Work
Whenever tensions between the United States and Iran spike, the same constitutional question resurfaces: does the president need congressional approval to use military force against Iran? The answer sits at the intersection of the Constitution, decades of statute law, and a web of executive orders that together form US–Iran foreign policy. This primer breaks those pieces apart.
The Constitutional Split
The framers divided war powers on purpose. Article I, Section 8 of the Constitution gives Congress the power to declare war, raise and support armies, and fund the military. Article II, Section 2 makes the president commander in chief of those armed forces. The result is a built-in tension: Congress decides whether the nation goes to war; the president directs the forces once committed.
In practice that line has blurred badly. Every major US military engagement since 1945 has been fought under either a UN resolution, an authorization for use of military force (AUMF), or the president's own Article II authority rather than a formal declaration of war. Iran policy operates inside that same gray zone.
The War Powers Act
Passed in 1973 over President Nixon's veto, the War Powers Act tries to reassert Congress's role. It requires the president to notify Congress within 48 hours of introducing armed forces into hostilities and to withdraw them within 60 days absent congressional authorization, with a 30-day extension possible.
Presidents of both parties have argued the law is unconstitutional and have largely treated it as advisory. For Iran, the act matters because it sets the procedural clock: any sustained kinetic action would require the executive to either obtain a new authorization or pull forces back.
Executive Orders and Sanctions
Most US–Iran policy is not military at all — it is economic. Since the 1979 hostage crisis, presidents have layered sanctions on Iran through executive orders grounded in statutes like the International Emergency Economic Powers Act (IEEPA). These restrict Iran's oil sales, block assets, and cut Iranian banks off from the dollar system.
Because sanctions are issued by executive order, a president can tighten or relax them without Congress, though many key authorities are codified in statute and cannot be repealed unilaterally. The nuclear deal framework illustrates the tug of war: the agreement lifted nuclear-related sanctions in exchange for limits on Iran's program, and a later administration withdrew from it and reimposed the sanctions.
The 2001 AUMF Debate
The 2001 AUMF authorizes force against those responsible for the September 11 attacks and associated forces. Some administrations have argued Iranian-aligned groups fall under it; critics, including members of Congress, reject that reading because Iran had no operational role in 9/11. A separate 2002 AUMF covering Iraq is even less relevant to Iran.
This matters because administration lawyers have used the 2001 AUMF to justify strikes against Iranian-backed militias as counterterrorism. If that authority does not actually cover Iran, then strikes would need to rest on the president's Article II self-defense power, which traditionally requires a threatened or actual imminent attack.
The Practical Limits
Constitutionally, the president can act to repel a sudden attack without waiting for Congress. A preemptive strike on Iran's nuclear facilities, however, would be a choice rather than a response, and almost every legal scholar agrees that requires congressional authorization. Congress has repeatedly considered — and declined to pass — an Iran-specific AUMF, which itself signals legislative discomfort with an open-ended grant of authority.
The structure is designed to make escalation hard. Sanctions can shift quickly because they sit in executive hands. Kinetic force cannot, because the Constitution and the War Powers Act together push the decision back toward Congress. Understanding that distinction is the key to reading any headline about US–Iran policy.