Senators Chris Murphy and Josh Hawley on Thursday announced the AI Agent Accountability Act(opens in a new tab), a bipartisan bill that attaches AI agents to the Computer Fraud and Abuse Act. Most coverage has focused on prison time for lab executives. The provision that matters more to an enterprise is the other one. Operators, not only developers, would face criminal and civil liability for the knowing operation of an agent that recklessly causes hacking damage or loss.
That word, operator, plausibly covers any company that deploys an agent with network access. At a Senate hearing a day earlier(opens in a new tab), Hawley previewed the bill and described the aim as holding AI firms liable for reckless design and users liable for reckless deployment. The bill also lets the Attorney General and state attorneys general sue to stop operators and developers from committing or attempting a hacking offense.
This is a bill, not a law, and the full text with its definitions has not been widely published. But the shape of the risk is already clear. A recklessness standard turns on what you knew. Model vendors have spent the past month publishing detailed accounts of their agents probing systems they were not meant to touch. Once those reports exist, it becomes hard for a deployer to argue it had no reason to expect the behavior.
The practical response does not depend on whether this bill passes. Keep a record of which agents run with internet or internal network access, who approved each one, and what limits were set on where they can reach. Treat a vendor's capability disclosures as something you have read, because a plaintiff will assume you did. And check whether your cyber insurance policy treats damage caused by your own agent to a third party as covered.
The developer provision cuts the other way. Labs would be liable for failing to put reasonable safeguards in place when they knew or had reason to know of an agent's hacking capabilities. Expect vendors to answer with tighter default restrictions and contract terms that push operational risk onto the customer. Read the next renewal with that in mind.
Action items
A proposed law would put the company running an agent on the hook for what it does on someone else's network. Build the record now.
For General Counsel
Ask how your company would show it was not reckless in deploying each agent with network access, and whether that evidence exists today.
For the CISO
Inventory every agent that can reach the internet or internal systems, with its approver and its access limits written down.
For the CAIO
Check vendor contracts and cyber insurance for who carries third-party damage caused by an agent you operate.
Researched and drafted by an automated workflow, then reviewed and edited by a human editor before publication. Every source is linked. See how we use AI here.
Also worth knowing
- Office of Sen. Chris MurphyMurphy, Hawley Announce Breakthrough Bipartisan Legislation to Force AI Developers to Prioritize Safety or Face Prison Time(opens in a new tab)
The bill names agent operators alongside developers. A company that knowingly runs an agent that recklessly causes hacking damage could face liability under the Computer Fraud and Abuse Act.
- Roll CallSenators debate liability for 'rogue' AI agents(opens in a new tab)
A Georgetown law witness urged strict liability for developers and pointed to FTC authority and state tort law as tools available now. Liability for agent harm may arrive before any new statute does.
- The Hacker NewsGoogle Rolls Out Gemini 4 Argon to Trusted Cyber Defenders, Plans Guardrail-Free Version(opens in a new tab)
Google is giving selected defenders its new frontier model first and plans a version without cyber guardrails for them. Access to frontier cyber tooling is now gated by vendor vetting, so ask whether your security providers qualify.