Versatile AI Risk Assessment
Office work and knowledge management

AI agent

Also known as: AI agent, agentic AI

An AI agent breaks a task into steps and completes it largely independently using tools, interfaces and its own permissions in business applications.

Explore the interactive model

Export handout

A concise PDF covering how the system works, its data flows and points to investigate, ready to share.

The explanations and measures describe the typical system design. Extensive personal changes add an appendix.

Understand the use case

What defines this use case?

An insurer uses agents to prepare claims, German municipalities have trialled them, and a telecommunications company uses them in customer service.

This page describes a typical system design. Actual data flows and permissions depend on your implementation.

System design
Agent with tool access
Ability to act
Can act within applications
Fields of use
insurance, public administration, telecommunications
Also known as
agentic system, workflow agent, research agent, browser agent, computer-use agent

How it works, step by step

System design and data flows

  1. Input data

    A task arrives, such as a claim, application or ticket.

    Claims, applications, tickets and websites come from outsiders. Agents controlling a browser or the whole screen analyse screen content as images.

  2. Processing

    A language model plans steps, calls tools and interfaces, and evaluates the responses.

    The model breaks an instruction into steps and selects suitable calls from the approved tools. An execution environment runs these calls and returns the results to the model. This can lead to further steps. Planning, actual tool execution and approval are distinct parts of the system.

  3. Results

    The agent creates cases, edits records or presents a complete decision proposal to a person.

    A generated result is newly worded or created. To assess it, the instruction and context on which it is based must remain identifiable.

  4. Use and impact

    Its actions change business applications immediately and can trigger payments, administrative decisions or customer responses.

    Write or execution permissions allow the system to change a state within an application. Model responses, tool calls and changes actually executed must therefore be considered separately.

Explore the system design: Select a component to see its task, incoming and outgoing data, and role in the use case. The guided walkthrough explains each phase. Then use Yes, Uncertain and No to represent your specific system variant.

How the system is built

15 review first27 clarify9 baseline threats

InputProcessingResultImpact Externalaccess 04 Input 21 Third-partycontent 10 AI model 60 Providerservice 11 Documentcollection 02 Memory 01 Training andfeedback 02 OtherAI agents 00 Tools andinterfaces 32 Result 213 Business appor equipment 00 person 00 Affectedperson 00 AI serviceswithout approval 01 Externalaccess 04 Input 21 Third-partycontent 10 AI model 60 Providerservice 11 Documentcollection 02 Memory 01 Training andfeedback 02 OtherAI agents 00 Tools andinterfaces 32 Result 213 Business appor equipment 00 person 00 Affectedperson 00 AI serviceswithout approval 01
  • Present
  • Depends on your system
  • Absent
  • Review first
  • To clarify

In this system design: 15 to review first, 27 to clarify, 9 baseline threats.

Architecture as a list

How it differs from similar use cases

Data and information

Input data and information sources

Claims, applications, tickets and websites come from outsiders. Claims, applications and customer requests concern specific people.

Processing and operating environment

The language model controlling the agent generally comes from another provider.

Storage and further use

Research agents search document collections or the internet; others work only with business application data. Some agents store intermediate results and findings for reuse in later tasks.

Results and data sharing

The agent calls programs, interfaces and searches itself, such as weather or policy data in claims handling. It creates cases, edits records or prepares payments, changing business applications.

Using a provider does not automatically determine where processing takes place. Storage location, subcontractors, deletion periods and use for training must be checked for the specific deployment.

Assess risks and determine measures

From understanding the system to analysing risks

  1. Define the system boundary

    Record data, participants, interfaces and permissions. Resolve uncertain characteristics in the model.

  2. Investigate threats

    Relate review candidates to actual data flows: what could happen, and who would be affected?

  3. Assess risk

    Assess impacts and likelihood in the deployment context. The number of review candidates is not a risk score.

  4. Provide evidence of measures

    Select appropriate controls, assign responsibilities and define effectiveness checks. Document residual risks and approvals.

Key threats in the application context

  • 4 particularly important
  • 11 typical
  • 27 depending on the system
  • 9 for every AI system

A total of 51 threats from the threat catalogue may be relevant to this use case.

Priority review points

  1. Prompt Injection: Indirect

    A crafted ticket or claim contains instructions the agent treats as a task. It executes them with its system permissions, for example disclosing data or approving a case.

  2. Excessive Agency

    The agent has write access across several business applications despite needing only read access. An error or injected instruction then changes records or triggers payments.

  3. Agentic AI / Autonomous Agents

    The agent chooses an unforeseen approach and executes it step by step. It has already processed many cases by the time someone reviews the results.

  4. Insecure Tool Design

    An agent's tool accepts arbitrary inputs without checking who initiated the call. The agent thus reaches data and functions unrelated to its task.

11 further review candidates in the typical design

Other relevant threats

  1. Backdoor ML Model

    Training data or an adopted base model can introduce hidden triggers for misbehaviour.

    Listed because of this characteristic

    • Uses another provider's model
  2. Sleepy Agent (Time/Event-Triggered Hidden Instructions)

    An instruction-following model can change behaviour at a particular time or event.

    Listed because of this characteristic

    • Performs natural language tasks
  3. Prompt Injection: Direct

    Users can override the system's working instructions through their inputs.

    Listed because of this characteristic

    • Performs natural language tasks
  4. Jailbreaks

    People requesting generated content may try to bypass intended limits.

    Listed because of this characteristic

    • Performs natural language tasks
  5. Meta Prompt Extraction

    Carefully crafted queries can reveal system instructions, which must therefore contain no secrets.

    Listed because of this characteristic

    • Performs natural language tasks
  6. Model Denial of Service

    Complex or high-volume inputs can exhaust model computing resources.

    Listed because of this characteristic

    • Generates its own text
  7. Privacy Attacks

    Targeted queries can recover some personal or protected training data from the model.

    Listed because of these characteristics

    • Processes personal data
    • Processes confidential data
  8. Sensitive Information Disclosure

    Confidential content can appear in answers, supplied context or logs.

    Listed because of these characteristics

    • Processes personal data
    • Processes confidential data
  9. Exfiltration from ML Application

    Protected data can leak through tools, network connections, storage or insiders.

    Listed because of these characteristics

    • Calls other programs or interfaces
    • Processes confidential data
  10. Factual Inconsistencies (Hallucinations)

    Generated text can invent facts or distort them during rewriting.

    Listed because of this characteristic

    • Generates its own text
  11. Misalignment

    The target metric can improve while the underlying objective is missed.

    Listed because of this characteristic

    • Determines its own work steps

Up to 27 further threats may apply, depending on your system design. Nine threats need to be reviewed for every AI system.

System features and open questions

Each Yes adds further threats to your checklist, up to 27 in total. If you cannot yet answer a question, include its threats in your review.

How many threats a Yes adds
  • Added by this Yes
  • Also requires a Yes to another question

How your system is built

  1. Generates content from open-ended requests10 threats, plus 2 only in combination with other characteristics
  2. Uses the Model Context Protocol (MCP)2 threats
  3. Uses operational feedback2 threats
  4. Searches its own document collection1 threat, plus 1 only in combination with other characteristics
  5. Learns from your own data1 threat, plus 1 only in combination with other characteristics
  6. Formulates answers from retrieved documents1 threat
  7. Remembers content beyond a single conversation1 threat
  8. Works with other AI agents1 threat
  9. Learns from examples with correct answers1 threat
  10. Processes text, images and speech together1 threat
  11. Generates code or queries1 threat
  12. One search store for several permission groups1 threat only in combination with other characteristics

How you operate the system

  1. Available to people outside the organisation4 threats, plus 2 only in combination with other characteristics
  2. Accepts queries directly through an interface4 threats
  3. Accessible over a network1 threat, plus 1 only in combination with other characteristics
  4. Incurs costs with each query1 threat
  5. Shares computing resources with other customers or applications1 threat
  6. Used alongside unapproved AI services1 threat

How your system is built

Does the system remember content from earlier conversations or tasks and reuse it later?

Some agents store intermediate results and findings for reuse in later tasks.

If yes, add

Does the system delegate tasks to other AI agents or incorporate their results?

At Allianz, seven specialised agents collaborate on each claim; simpler agents work alone.

If yes, add

Does the system process several input types together, such as text with images or speech?

Agents controlling a browser or the whole screen analyse screen content as images.

If yes, add

Does the system generate code, scripts or database queries for further use?

If yes, add

How you operate the system

These questions arise for almost every AI system.

Do you pay per query or unit of computing time, so costs increase with use?

Each step calls the language model again; a loop can rapidly increase costs.

If yes, add

Controls and implementation

Measures for the priority review areas are expanded. Each linked measure explains how to implement it.

Review priorityPrompt Injection: Indirect3 measures
Review priorityExcessive Agency3 measures
Review priorityAgentic AI / Autonomous Agents3 measures
Review priorityInsecure Tool Design3 measures
Backdoor ML Model2 measures
Sleepy Agent (Time/Event-Triggered Hidden Instructions)3 measures
Prompt Injection: Direct3 measures
Jailbreaks2 measures
Meta Prompt Extraction2 measures
Model Denial of Service3 measures
Privacy Attacks3 measures
Sensitive Information Disclosure3 measures
Exfiltration from ML Application3 measures
Factual Inconsistencies (Hallucinations)3 measures
Misalignment3 measures

Controls for the remaining threats are available on their pages in the threat catalogue.

AI Act provisions

When AI Act provisions apply
  1. Art. 4: AI literacy

    For every AI system Applies since 2 February 2025.

  2. Art. 53 para. 1 point b, Annex XII: Embedded general-purpose model

    Depending on use Review trigger since 2 August 2025.

  3. Art. 50 para. 1: Disclosure of AI interaction

    In typical use Review trigger since 2 August 2026.

  4. Annex III no. 5 point a: Public assistance benefits

    Depending on use Review trigger from 2 December 2027.

Applies to every AI system

Art. 4: AI literacy

Applies if staff or appointed representatives operate or use AI systems.

Applies since 2 February 2025.

Obligations and details for Art. 4: AI literacy
Who bears the obligations
Provider, Deployer, Product manufacturer, Provider of a general-purpose AI model

Detailed obligations

May apply in typical use

Art. 50 para. 1: Disclosure of AI interaction

Applies if the agent communicates directly with customers or citizens and it is not obvious that an AI is responding.

Applies since 2 August 2026.

Obligations and details for Art. 50 para. 1: Disclosure of AI interaction
The general condition is
Applies if people directly write or speak with the system and it is not obvious that they are interacting with AI.
Who bears the obligations
Provider, Product manufacturer

Detailed obligations

May apply in particular uses

Annex III no. 5 point a: Public assistance benefits

Applies if the agent checks applications for public assistance benefits or prepares decisions on them for an authority.

Applies from 2 December 2027.

Obligations and details for Annex III no. 5 point a: Public assistance benefits
The general condition is
Applies if authorities or bodies acting for them use the system to assess eligibility for public benefits and services, or to grant, reduce or recover them.
Who bears the obligations
Provider, Deployer, Product manufacturer

Detailed obligations

Art. 53 para. 1 point b, Annex XII: Embedded general-purpose model

Applies if your organisation builds the agent itself and controls it with a large language model or another third-party general-purpose model.

Applies since 2 August 2025.

Obligations and details for Art. 53 para. 1 point b, Annex XII: Embedded general-purpose model
The general condition is
Applies if another provider's general-purpose AI model is incorporated, such as a large language model.
Points to consider
The model provider bears its obligations. It must give you the Annex XII information; use it for your own documentation.
Who bears the obligations
Provider of a general-purpose AI model

Detailed obligations

Classify your system with the quick checker All obligations in the obligations compass

Cross-cutting threats

Review these threats for every AI system, whatever its purpose.

Why these threats always belong on the checklist

Atypical system features

View 1 further question

If any of these features does apply to your system, add the listed threats.

Sources

Related use cases

Also in the field of Office work and knowledge management

Often used together with

Updated: 30 September 2026. Review checklist rules version 0.3.2, threat catalogue version 2026.10.24.2. How these pages are structured