AI developers get legal shield for reporting safety risks to feds
H.R. 9477 — AI Incident Reporting Act · Filed by Nathaniel Moran (R-TX) · 3 cosponsors · Introduced Jun 25, 2026 · Referred to committee
Your members of Congress
Enter a ZIP to see where your representative and both senators stood on this bill.
Looked up on this device — your ZIP is never stored on our servers.
What it does
This bill requires AI model developers to report to the Department of Commerce within 7 days when their AI systems exhibit dangerous behaviors—such as attempting to evade human control, accessing unauthorized systems, enabling cyberattacks, or accelerating weapons development. The Commerce Department will set thresholds for which AI models must comply, establish reporting procedures, and can impose civil penalties up to $2 million per violation. Reports are protected from civil lawsuits and regulatory enforcement, but the government can use them to respond to national security threats.
Why we flagged it
The bill's core mechanism is mandatory incident reporting for dangerous AI capabilities—a legitimate safety measure. However, the operative effect is also a broad liability shield: developers who report are protected from civil suits and regulatory enforcement, which captures private benefit alongside the public safety goal.
What the text implies
- Developers gain immunity from civil liability for AI harms if they report—but only if the harm meets the narrow 'reportable activity' definition. Harms outside that definition (e.g., bias, privacy violations, labor displacement) remain unreportable and unshielded, creating a perverse incentive to avoid reporting non-national-security harms.
- The 'good faith reporting' language and immunity from regulatory enforcement may discourage the Commerce Department from using reports to strengthen AI safety rules, since doing so could be read as enforcement against the reporting developer.
- State and local governments are explicitly barred from using reported information for enforcement, potentially preempting state AI safety laws and consumer protection actions.
- The Secretary has broad discretion to designate 'covered models' and add new reportable activities via rulemaking, but the bill contains no sunset, public comment requirement, or congressional approval mechanism for these expansions.
- Congressional notification is required only for 'imminent or ongoing' risks (48 hours) or within 30 days for other reports—but Congress receives no enforcement authority or veto power, limiting legislative oversight.
Section numbers refer to the bill text the analysis read — linked under Primary records below.
Who it affects
Citizens gain transparency and early warning of dangerous AI capabilities that could threaten national security or public safety, and the reporting requirement creates accountability for developers. However, the broad immunity from civil liability and regulatory enforcement means citizens harmed by AI incidents may lose their right to sue developers, and the government's ability to act on reports is limited to national security/safety responses—not consumer protection or other harms.
Who stands to gain
- AI model developers (liability shield for reported incidents)
- Large AI companies with resources to comply with reporting (smaller competitors face higher complian
Named in the bill
Department of Commerce, AI model developers, House Committee on Energy and Commerce, House Committee on Science, Space, and Technology, Senate Committee on Commerce, Science, and Transportation, Permanent Select Committee on Intelligence, Select Committee on Intelligence, Attorney General
Where it stands
3 cosponsors: 3 Democrats.
- Jun 25, 2026 — Introduced · Congress.gov: “Introduced in House”
- Jun 25, 2026 — Referred to House Committee on Energy and Commerce · Congress.gov: “Referred to the House Committee on Energy and Commerce”
Dates and quoted wording are Congress.gov's action record; the timeline shows status changes, not every procedural step.
Money around this bill
2 lobbying clients named this bill on 2 disclosure filings across 1 quarter, Jun 2026 to Jun 2026. Those filings disclosed $198,894 in lobbying spend. A filing names 20 bills on average, so that figure is what each filing reported, not a share belonging to this bill.
More lobbying clients named this bill than 41% of bills with at least one filing.
Nathaniel Moran, the sponsor, reported $856,691 in PAC receipts in the 2026 cycle.
- The Ai Policy Network Inc. — $188,894 on 1 filing
- The Alliance for Secure Ai Action — $10,000 on 1 filing
Lobbying Disclosure Act filings through Jul 20, 2026. A filing shows who paid to lobby on a bill it names, not what changed.
How this was measured
Analysis — Quorum's AI read the bill text published by Congress.gov (14,396 characters) on Jul 2, 2026. Section numbers in the findings refer to that text, linked below; transparency and hidden-provision scores are compared against the median of 16,222 analysed bills.
Status and sponsors — Congress.gov's bill record — actions, committee referrals and cosponsors — loaded nightly. The timeline shows status changes, not every procedural action.
Money — Senate Lobbying Disclosure Act filings whose specific-issue field names this bill for quarters ending Jun 2026 to Jun 2026. A filing's amount is reported whole beside the median number of bills a filing names; it is never divided across them. PAC receipts are FEC-reported contributions to the sponsor's candidate committee in the 2026 cycle.
As of — lobbying records through Jul 20, 2026 · page rendered 2026-10-20.
“AI developers get legal shield for reporting safety risks to feds” QuorumCivic. https://share.quorumcivic.app/bill/119/hr9477 Report an error
The week in bills
One email, Sunday: what Congress passed, what it changed, and who paid.
One link arrives to confirm the address. It is used for this email and nothing else, and every issue carries an unsubscribe link.