INQUIRING LINE

If AI agents quietly pass a task around in a circle, how could anything spot the loop when each hand-off looks fine?

How can detection systems identify loops across sequences of delegations?

This explores how a monitor could notice that a task has been handed from agent to agent and eventually back around, like the 'Telephone Loop' attack, when every individual hand-off looks harmless.


This explores how a monitor could notice that a task has been handed from agent to agent and eventually back around, even though every individual hand-off looks harmless. The corpus has no tested loop detector. It does explain why the obvious approaches fail and what a working one would need to track. The threat is concrete: the Telephone Loop is an attack that abuses cross-agent delegation to make agents pass work around in circles, and it needs multiple agents to exist at all Can agents be tricked into delegating work in circles?.

The first lesson is that a loop is a property of the whole sequence, not of any single step. Per-action guardrails are structurally unable to state a rule that depends on prior history. Only stateful monitors that follow composed multi-party behavior can check it Can stateless checks ever catch sequence-level constraint violations?. Skill scanners show the same weakness. ColluSkill reaches about 96% attack success because scanners score each skill alone, so an attacker can polish every piece while the chain-level intent stays intact Can attackers evade skill scanners by refining individual skills?. A delegation ring works the same way: each 'please handle this' is fine, and only the circle is the problem.

The second lesson is what to track. One line of work argues that the unit of defence should be a set of actions linked by observed transfers, task authority and response history. Membership should be revised as evidence accumulates Should defence units span multiple executions and agents?. Applied to loops, delegations are the transfers, and a loop is a chain of transfers that returns to an agent that already held the task, with no new authority or visible progress. That reading is my extension of the idea, not something the paper tests. Provenance also has to live in that structure, not in what agents say. Monitors that read text as if one author wrote it lose track when agents paraphrase reasoning they picked up from context, so origin is erased at the boundary Can chain-of-thought monitors detect reasoning that originates elsewhere?.

The hard part is doing this before you know which actions belong together. The same research names this 'prospective episode discovery' as the central unsolved problem. It reports no conclusive result on whether discovery can run at an acceptable false-alert cost Can defenders discover agent episodes without knowing membership in advance?. A second trap is that cycles aren't inherently suspicious. Distilled reasoning models show about five cycles per sample in their hidden-state reasoning graphs, against near zero in base models, and more cycles go with better accuracy Do reasoning cycles in hidden states reveal aha moments?. That finding concerns one model reconsidering its own answer, not delegation between agents. It does suggest that a good delegation-loop detector shouldn't flag any cycle. It should flag cycles that go around without making progress.


Sources 7 notes

Can agents be tricked into delegating work in circles?

Research identifies a novel MAS-specific attack that weaponizes cross-agent delegation to form task cycles, distinct from applying existing attacks like prompt injection to teams. The mechanism requires multiple agents and has no single-agent counterpart.

Can stateless checks ever catch sequence-level constraint violations?

Per-action checks are structurally unable to state constraints that depend on prior history. Only stateful monitors tracking composed multi-party behavior can verify the behavioral envelopes that prevent individually permissible actions from collectively violating system-level safety.

Can attackers evade skill scanners by refining individual skills?

ColluSkill combines chain planning with scanner-feedback refinement to reach 96% average attack success. The approach works because scanners score skills individually, allowing feedback to reduce suspicion per skill while chain-level semantics remain intact.

Should defence units span multiple executions and agents?

The operational unit of defence should be a set of actions linked by observed transfers, task authority, and response history, with membership revised as evidence accumulates. Isolated review loses relevant context that spans multiple executions.

Can chain-of-thought monitors detect reasoning that originates elsewhere?

In RAG and multi-agent pipelines, models paraphrase reasoning from context without attribution, erasing provenance. Monitors treating the trace as single-authored evaluate mixed-authorship reasoning without detecting its external origin, creating a blind spot at the context-window boundary.

Show all 7 sources
Can defenders discover agent episodes without knowing membership in advance?

Research identifies prospective discovery—grouping actions before membership is supplied—as the key bottleneck in coordinated agent defense. The paper proposes matching known-groups and discovered-episodes arms on reviewer workload, but reports no conclusive result on whether discovery can be done at acceptable false-alert costs.

Do reasoning cycles in hidden states reveal aha moments?

Distilled reasoning models show ~5 cycles per sample versus near-zero in base models, and cyclicity correlates with accuracy. These cycles in hidden-state reasoning graphs directly map to RL-trained models' documented aha moments—moments when models reconsider intermediate answers.

Papers this line draws on 8

The research behind the notes this line reads — ranked by how closely each paper relates.