Skip to content

GCRI · Kecerdasan Buatan dan Sistem Otonom

Sistem agentik

Agentic AI sistem pursue goals by planning and taking actions: calling tools, browsing, writing and running code, or operating other software, sometimes over long tasks with little supervision. Autonomy brings usefulness and new failure modes, from compounding errors to misuse of granted permissions. This page sets out how agents fail, how their actions can be bounded and overseen, and what evidence serves those who build, deploy and govern them.

01Daftar

Agentic systems on the record.

02Pertanyaannya

Agentic systems: how the risk develops.

Tool access, delegated authority and safe execution. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.

Mekanisme

Errors compound over steps

Each step in a long task can go wrong, and an early mistake shapes later actions. Small per-step error rates add up over many steps.

Mekanisme

Permissions define the blast radius

An agent can only do harm with the access it has been given. Broad credentials, write access and payment rights turn errors or manipulation into real-world consequences.

Mekanisme

Untrusted inputs steer behaviour

Agents read web pages, documents and messages that may contain instructions. Prompt injection can redirect an agent to act against its user.

Mekanisme

Oversight must be designed in

Humans cannot review every action of a fast agent. Approval steps for consequential actions, logging and the ability to stop and roll back are design choices.

03Pantau

Agent oversight console.

Layar yang akan digunakan sebuah tim untuk mengikuti subjek ini: ukuran, status, dan keputusannya. Nama adalah contoh dan nilai bersifat ilustratif.

Agent oversight console

Agentic systems · Agent sandbox · Session AG-6627

Human approval pendingGCRI · Kecerdasan Buatan dan Sistem Otonom

Tool calls

  1. 10:34Infosearch(documents) · read-only
  2. 10:51Inforun_model(flood_nowcast) · sandbox
  3. 10:51Gerbangsend_message(external) · needs approval
  4. 10:53Errorwrite_file(outside workspace) · denied

Kebijakan

Lingkup
workspace only
External actions
human approval
Spend limit
43 units
Kill switch
Armed

Actions by approval class

050100count this weekOtomatisDicatatDisetujuiDeniedDieskalasi
Agent oversight console: the screen’s structure, terms and states for Agentic systems.Nama contoh dan nilai ilustratif; sebuah rancangan, bukan catatan atau sistem yang aktif.
04Di seluruh domain

Agents that act need guardrails in every domain they touch.

Agentic system studies are designed for the seri Teknologi Eksponensial. The OWASP Top 10 for LLM applications lists failure modes such as excessive agency and prompt injection; the page describes them without exploit detail.

  • Incident reports involving agents.
  • Designs for oversight and permission scoping.
05Metode dan bukti

How agentic systems is modelled, measured and tested.

Model, asumsi, data, dan ketidakpastiannya, dalam bentuk yang akan diperiksa ilmuwan atau insinyur. Strukturnya mengikuti metode yang dipublikasikan. Nilai yang digambar bersifat ilustratif, bukan temuan.

Model sistem

The couplings between the systems in agentic systems: signs of influence, a reinforcing and a balancing loop, and cross-links where stress jumps.

++−+Kecerdasan buatanDataKomunitasEkonomiR penguatB penyeimbang
Causal loop diagram from the page’s systems; signs show the direction of influence. Illustrative structure for a system dynamics or network model, not estimated couplings.
Prinsip panduan FAIR · GO FAIR dan FORCE11W3C PROV · World Wide Web ConsortiumPanduan penanganan ketidakpastian secara konsisten · IPCCCEOS Analysis Ready Data · Committee on Earth Observation Satellites
06Indikator

Apa yang diukur, dan seberapa baik.

Setiap indikator membawa satuan, frekuensi, jenis sumber di baliknya, dan label bukti yang akan dibawa suatu nilai. Tidak ada nilai yang ditampilkan: sebuah program menyediakannya berdasarkan wewenangnya sendiri.

IndikatorUnitKadensiJenis sumberLabel
Task success rate on agent benchmarkspercent of tasks completed correctlyper evaluationAgent benchmark resultsDILAPORKAN
Actions requiring human approvalpercent of consequential actionsper deploymentDeployment configurationDINYATAKAN
Prompt injection success ratepercent of attempts succeedingper evaluationSecurity testingTERAMATI
Agent incidentscount by severitysetiap bulanIncident reportsDILAPORKAN
Actions logged and attributablepercent of agent actionsper deploymentAudit logsTERAMATI
Mean task length before human interventionsteps or minutesper evaluationEvaluation logsTERAMATI
07Sumber

Asal bukti.

Set data publik bernama dan catatan kelembagaan, masing-masing dengan kelas lisensinya. Sumber berdasarkan perjanjian hanya digunakan sesuai ketentuannya dan tidak pernah diterbitkan ulang.

SumberApa yang diberikannyaKelas lisensi
OWASP Top 10 for LLM Applications and agentic security guidanceRisks such as prompt injection and excessive agencyOpen, CC BY-SA 4.0
Published agent benchmarks such as SWE-bench and related suitesTask-based evaluation of agentsOpen, licence per benchmark (to check)
Kerangka Manajemen Risiko AI NIST (NIST AI Risk Management Framework)Practices for governing and measuring AI riskPublic domain, US government
AI Incident DatabaseReported incidents involving AI sistemOpen, licence to check
Developer system cards describing agent safeguardsDeveloper-reported agent evaluations and controlsPublic documents, terms per developer
08Keputusan

Siapa yang memutuskan, dan apa yang dilayani bukti.

Studio Kecerdasan Buatan dan Sistem prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.

Siapa yang memutuskanPertanyaannyaBukti yang dilayani halaman ini
Deploying organisationsWhich actions an agent may take alone and which need approvalPermission patterns; evaluation results
Security teamsHow to protect agents from manipulationInjection testing; incident evidence
RegulatorWhat oversight to require for autonomous AI actionsOversight design evidence

Keluaran yang dihasilkan topik ini

  • Permission and approval design patterns for agents
  • Agent evaluation protocols covering long tasks
  • Prompt injection test suites for deployments
  • Logging and rollback requirements
09Pertanyaan inti

What designers and evaluators ask.

  • What actions can the agent take, with whose authority, and which are reversible?
  • How does it behave when instructions are ambiguous, conflicting or malicious?
  • Can a human see what it is doing, understand why and stop it in time?
  • How do errors compound over long sequences of steps?
10Mekanisme

How agents fail.

An agent combines a model’s reasoning with permissions in the world. Small errors in early steps can compound across a long task. Agents can misinterpret goals, pursue them in unintended ways or take shortcuts that satisfy a metric but not the intent. Content the agent reads, such as a web page or document, can contain instructions designed to hijack it, an attack known as prompt injection.

The more permissions an agent holds, the larger the potential harm. Sistem that coordinate several agents add further failure modes, as agents pass errors to each other or interact in unforeseen ways.

11Metode dan data

Designing for safe execution.

  1. 01

    Least privilege

    Granting only the permissions a task needs, with sandboxes and spending or action limits, drawing on keamanan siber dan kriptografi.

  2. 02

    Human oversight points

    Requiring confirmation for consequential or irreversible actions. Too many prompts lead to rubber-stamping, so placement matters.

  3. 03

    Task-based evaluation

    Testing agents on realistic multi-step tasks in controlled environments, using Evaluasi AI dan rekayasa penjaminan. Simulated environments miss some real-world complexity.

  4. 04

    Logging and audit

    Recording actions and reasoning traces so incidents can be reconstructed. Traces may not fully reflect how a model reached a decision.

13Where this page’s references

Where this page’s references lead.

Badan dan dokumen yang menjadi acuan halaman ini. Status dan edisi berubah; setiap tautan menuju badan penerbitnya.

14Pertanyaan

Tanya jawab.

What is an AI agent?
An AI system that pursues goals by planning and taking actions, such as using tools, browsing or running code, with some degree of autonomy.
What is prompt injection?
An attack in which instructions hidden in content the AI reads, such as a web page or document, cause it to act against its user’s intent.
How can agent risk be reduced?
By limiting permissions to what the task needs, requiring approval for consequential actions, logging all actions, testing against manipulation and keeping the ability to stop and undo.
Should agents ever act without human approval?
For low-consequence, reversible actions within tight limits, often yes. For consequential or irreversible actions, the design question is where and how a human confirms.
Can agents be evaluated before deployment?
Partly, in controlled environments with realistic tasks. Monitoring after deployment remains necessary because real environments are more varied.
Does the platform build agents?
Its work is evaluation and method. Any build work for Consortium projects runs through Foundry under its own governance.
LaporanBerkontribusi

Kontribusikan bukti dari halaman ini.

Laporan 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.

GCRIKecerdasan Buatan dan Sistem OtonomTeknologi EksponensialBukti Labs
Kecerdasan Buatan dan Sistem Otonom

Bawa metode, dataset, atau pertanyaan.

Informasi dan pertanyaan sudah terbuka hari ini. Sebuah pertanyaan menerima nomor referensi dan menyebutkan langkah berikutnya; lamaran, pembayaran, alokasi komputasi, dan pendaftaran hanya dibuka ketika tim, ketentuan, dan kapasitas tinjauannya tersedia.