Skip to content
AI

Why can each tool my agent calls be authorized while their sequence is not?

88

Opportunity

AI agents execute tool calls that each pass normal permission checks in isolation. But a session-level sequence of individually permitted calls can compose into a capability no one approved: read an environment file, search for credential patterns in it, then POST the result to an external endpoint. Traditional authorization operates at the single-call boundary and has no model of what a sequence enables. The Cline incident in February 2026 demonstrated this concretely: a malicious GitHub issue chained individually valid reads and writes into a package install that reached 4,000 developer machines. Intent-governed authorization at the sequence level does not exist as a production primitive today.

Why it matters

Sequence-level authorization is the structural gap between granting tool permissions and actually bounding what an agent session can do.

How I score the opportunity

The Opportunity Score is my own read, not a measurement: how much it hurts, how often it bites, and how little exists to solve it today. Higher means I think it is more worth building.

Severity9/10

How much pain it causes when it shows up.

Frequency8/10

How often people actually run into it.

Whitespace9/10

How little good tooling exists for it today.

More problems worth solving