SYNTHESIS NOTE
Topics›Agents Multi Architecture›this note

Why do single-message classifiers miss cross-agent harms?

Can prompt classifiers detect malicious intent when harm emerges only across multiple agent interactions? The question reframes security from checking individual messages to tracking how content flows and transforms through a multi-agent system.

Synthesis note · 2026-09-23 · sourced from Agents Multi Architecture

SafeFlow's authors say the fragmentation failure "is better understood as a semantic information-flow problem than as a single-turn prompt classification task." The sentence changes the unit of analysis. A prompt classifier takes one text and asks whether it is harmful. A flow view takes a piece of content, or a request, and asks where it came from, what has happened to it and where it is going. The introduction says why the second view is needed: "planner decisions, inter-agent messages, and tool-side effects jointly determine system behavior." A classifier sits at one of those three and sees a slice. In the fragmentation example (Can task decomposition hide harmful intent across agents?) the harm is defined over the path through all of them.

The vocabulary comes from software security, where information-flow control and taint tracking label data at its source and follow the label wherever the data goes. That background is not in the excerpt, but the paper's own terms, "taints" and "information-flow", invoke it. What the paper adds is the word "semantic". In an LLM system content is re-expressed in natural language at every hop, so a label cannot simply ride on the string. It has to attach to something that survives paraphrase, which is the question taken up in How does SafeFlow track sensitivity through agent rewrites?.

The design consequence is that better classifiers do not close a gap that classification cannot see. The defenses ChannelGuard lists (IBProtector, SmoothLLM, Llama Guard, perplexity thresholds) are input classifiers, as Do internal agent hops in pipelines need security monitoring? records. ChannelGuard's own remedy, a gate on every hop, keeps the classification unit and multiplies the checkpoints. The flow framing says the missing piece is not more checkpoints but a label that connects them. Whether coverage or flow is the better investment is open; an open tension in ops/tensions/ records it. The change of unit has a second answer elsewhere in the vault: Should defence units span multiple executions and agents? replaces the isolated action with a set discovered from observed transfers whose membership stays revisable, where a SafeFlow taint is set once at the root request.

The counterargument is cost and sufficiency. Flow tracking needs labels, a graph and a validator, while classification is cheap and probably enough for injection-shaped payloads that sit in one message. That points toward layering, not replacement.

What the excerpt does not give. "Semantic taint" is defined only as "structured", and there is no comparison against classification baselines.

Inquiring lines that read this note 26

This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.

Does multi-agent architecture create security vulnerabilities single-agent defenses can't address? How should persistent agent-authored code be governed and shared? Can sequences of locally safe agent actions violate system-level constraints? How do prompt injection attacks succeed or fail across defenses? How do users build accurate mental models when agent reasoning is partially hidden? How do agents coordinate to violate constraints despite individual-level safeguards? How does workflow position amplify security failures in multi-agent systems? What evidence best independently verifies agent behavior for safety? Can prompt engineering achieve genuine reasoning improvements without introducing user bias? How should agent identity and authorization work across organizational boundaries? Why do autonomous agents report success despite actually failing? How can merchant-funded agents remain loyal to consumer interests in digital commerce? Is mimicking human communication the best design approach for conversational AI?

Related concepts in this collection 7

This note in its neighbourhood — explore the map, then jump to a related concept in the list below.

Concept map
18 direct connections · 121 in 2-hop network ·medium cluster Open in graph ↗

Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph

your link semantically near linked from elsewhere

Related papers in this collection 8

Papers most semantically related to this note, ranked by cosine similarity in the embedding space.

Original note title

malicious cross-agent propagation is a semantic information-flow problem rather than a single-turn prompt classification task