GRF · AI and Digital Governance
Autonomous agents and liability
AI agents now plan and take actions across software, payments and physical systems with limited human input. When an agent causes harm, existing liability rules must decide who pays: the developer, the deployer, the user or the operator of the platform it acted on. This page sets out how autonomy strains liability and oversight, the records that show it, and who decides how responsibility is assigned.
Autonomous agents and liability on the record.
Autonomous agents and liability: how the risk develops.
Action boundaries and accountability. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
Actions outrun intent
An agent pursuing a goal can take steps its user did not foresee or authorise. Fault-based liability struggles when no person intended or could reasonably foresee the harmful action.
Many hands, unclear fault
The model, the agent framework, tool providers, the deploying firm and the user all contribute. Proving which defect caused harm is costly for claimants without access to records.
Permissions define exposure
What an agent can access, spend or change sets the size of possible harm. Limits, confirmations and kill switches are governance choices made at deployment.
Law adapts slowly
Product liability, contract and tort law are being reinterpreted for software and AI. Until courts and legislatures settle questions, uncertainty itself shapes deployment.
Public algorithm register.
The screen a team would use to follow this subject: its measures, states and decisions. Names are examples and values are illustrative.
Public algorithm register
Autonomous agents and liability · Algorithm register · Quarter 2
Registered systems
| Benefit fraud flagging | Social agency | అధికం | Missing | Partial |
| Permit triage | Planning | Limited | పూర్తయింది | అవును |
| School placement | Education | అధికం | పూర్తయింది | అవును |
| Chat assistant | Tax office | Minimal | పూర్తయింది | వర్తించదు |
Oversight action
- వ్యవస్థ
- Benefit fraud flagging
- Required
- impact assessment, appeal route
- Deadline
- 77 days
- అధికారం
- Oversight body
Complaints about automated decisions
What is measured, and how well.
Each indicator carries its unit, its cadence, the kind of source behind it and the evidence label a value would carry. No values are shown: a programme supplies them under its own authority.
| Indicator | Unit | Cadence | Source type | Label |
|---|---|---|---|---|
| Jurisdictions treating software as a product for liability | count | on change | Legislation | Published statistics |
| Court decisions on AI-caused harm | count by type | annual | Case law databases | Published statistics |
| Agent incidents reported | count by harm type | monthly | Incident databases | నివేదించబడింది |
| Deployments with documented permission limits | share of surveyed deployments | periodic | Surveys and audits | DECLARED |
| Insurance products covering AI liability | count of offerings | annual | Market reports | నివేదించబడింది |
| Regulatory guidance on agentic AI | count of documents | annual | Regulator publications | Published statistics |
How autonomous agents and liability is governed: instruments, mandates and commitments.
The instruments, mandates, actors and accountability arrangements a policymaker, diplomat or development agency works with, citing the agreements that set them. Structures follow the frameworks named. Any state or progress drawn is illustrative, not a record.
Policy instrument matrix
The kinds of instrument available on autonomous agents and liability, by level of government and cooperation.
| Instrument type | Local | జాతీయ | ప్రాంతీయ | ప్రపంచవ్యాప్త |
|---|---|---|---|---|
| Regulatory | Zoning, building codes | Laws, standards, licensing | Harmonised rules | Conventions and treaties |
| Economic | Local levies, grants | Budget lines, taxes, insurance schemes | Risk pools, regional funds | Financing mechanisms |
| సమాచారం | Local warnings | Disclosure, early warning, statistics | Data sharing arrangements | Global monitoring and reporting |
| Institutional | Local committees | Lead agencies, coordination councils | Regional bodies and secretariats | Multilateral mandates |
| Cooperative | Community agreements | Partnership compacts | Memoranda and joint programmes | Agreements and joint commitments |
Where the evidence comes from.
Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.
| మూలం | What it gives | Licence class |
|---|---|---|
| EU revised Product Liability Directive | Liability rules including software and AI systems as products | Public, EU reuse terms |
| Law commission and parliamentary reports on AI liability | Analysis of liability options for AI and automated systems | Public records, terms per body |
| OECD AI Incidents Monitor | Recorded incidents involving AI systems | Free, OECD terms |
| UK Automated and Electric Vehicles Act and Automated Vehicles Act | Liability allocation for automated vehicles | Open Government Licence |
| Court judgment databases | Decisions on harm involving automated systems | Public records, terms per court |
Who decides, and what the evidence serves.
AI and Digital Governance prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| Who decides | The question | Evidence this page serves |
|---|---|---|
| Legislatures and law commissions | How liability rules apply to autonomous systems | Comparative regimes and case evidence |
| Deploying organisations | What an agent may do and what controls apply | Control practice and incident evidence |
| Insurers | Whether and how to cover AI liability | Incident patterns and legal developments |
| Courts | Who is liable for harm in a specific case | Records presented by parties; the page serves context only |
Outputs this topic produces
- Comparative notes on liability rules for software and AI
- Guide to permission limits and controls for agent deployments
- Dialogue briefs on allocating responsibility in multi-party AI chains
- Questions for legislatures on agent liability
What experts ask about autonomous agents.
- What actions is this agent permitted to take, and how are those limits enforced technically?
- When an agent causes harm, who is liable: the developer, the deployer, the user?
- How can an agent’s actions be traced, reviewed and reversed?
- How should agents interact with other agents, and who governs those interactions?
Why agents raise new governance questions.
Most governance frameworks were built for systems that advise a person who then acts. Agents collapse that gap, and with it one of the main points at which errors were caught. Why now: AI agents that act on behalf of people and organisations raise questions of liability that existing rules did not foresee, and legislators are still working through them. The platform is designed to compare emerging approaches and to record open questions for decision holders, without giving legal advice.
Action without review
Agents can act faster and more often than people can review, so errors can multiply before anyone notices.
Agents meeting agents
Interactions between automated systems can produce outcomes no one designed, as seen in automated trading.
Unclear responsibility
Existing liability rules assume a human or company acted; agents complicate who that is.
Instruments for bounding agents.
- 01
Permission and scope controls
Technical limits on what agents can access and do, studied under AI evaluation and assurance engineering. Limits: agents may find unintended routes around controls.
- 02
Logging and reversibility
Recording actions and designing them to be undoable where possible. Limits: some actions cannot be reversed.
- 03
Human approval thresholds
Requiring human sign-off above defined risk levels. Limits: can slow operations and invite approval fatigue.
- 04
Liability analysis
Comparing how legal systems allocate responsibility. Limits: law is still developing.
How it is studied, and what the methods cannot say.
- 01AI evaluation and assurance engineeringThird-party audit scope · Fairness testing in public systems · Post-deployment monitoringApplied here
- 02Artificial intelligence and machine learningHow models fail in deployment · Reading model documentation · Agent architectures explainedApplied here
- 03Policy, institutional and decision scienceComparing AI regimes · Value chain accountability mapping · Forum and mandate mappingApplied here
- 04Digital identity and public digital systemsAssurance levels for public services · Minimal disclosure · Exclusion analysisApplied here
ప్రశ్నలు మరియు సమాధానాలు.
What is an AI agent?
Who is liable when an AI agent causes harm?
What controls limit agent harm?
Can an AI agent be legally responsible?
How can agent actions be kept within bounds?
Does the platform test agents?
Why do agent interactions matter?
ఈ పేజీ నుండి ఆధారాలను అందించండి.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-GRFSend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGlobal Risks ForumSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
వ్యక్తిగత డేటా, సున్నితమైన మౌలిక సదుపాయాల వివరాలు లేదా పంచుకునే హక్కు మీకు లేని దేనినీ ఎప్పుడూ పంపవద్దు. సహకారం ఉపయోగానికి ముందు సమీక్షించబడుతుంది; దానిని పంపడం వల్ల రచయిత్వం లేదా సంపాదకీయ హక్కులు లభించవు, మరియు స్పాన్సర్షిప్ ఎప్పుడూ ఒక నిర్ధారణను కొనలేదు.
Bring a governance question to the Forum.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
చట్టపరమైన పత్రాలు.
Show all 18 legal documents
ఈ సైట్లోని మ్యాప్లు, డేటా మరియు చిత్రాలు సందర్భం మరియు సాధారణ సమాచారం కోసం చూపబడతాయి. అవి సలహా, ముందస్తు అంచనాలు లేదా హెచ్చరికలు కావు; సమాచారం యొక్క పరిమితులు నిరాకరణలు మరియు డేటా నోటీసులలో వివరించబడ్డాయి.