Skip to content
PERMISSION/PROTOCOL
Back to incident tracker

2026-11-14

HighPrimary

Agent Runtime Executed Simulated Bank Transfers After Conditions Changed or Consent Was Withdrawn

Controlled Agno banking tests executed simulated transfers after reserve conditions changed or consent was withdrawn, exposing execution-time authority gaps.

Agno 3.1.12 banking agent runtimeGovernance bypassControlled research on stale conditional approval and pending-confirmation revocationCloned benchmark banking state and native Agno 3.1.12 tool continuations; not a production banking deployment

What happened

The runtime committed a previously confirmed transfer after a reserve condition changed, and in separate episodes executed an earlier transfer before processing text revising its authority.

Why it matters

No production impact established. Native banking tools committed effects in isolated cloned state; the simulated effects establish an authorization mechanism, not real financial loss.

Missing authorization check

Validate current scoped consent, revocation state and reserve conditions immediately before committing the exact transfer.

Would PP block it?

A grant tied to the latest decision and exact transfer arguments could be rejected when revoked or when its reserve predicate is no longer true. This depends on authenticated decision updates, trustworthy state and complete mediation. The paper does not evaluate Permission Protocol or establish prevention efficacy.

Incident analysis

Timeline and technical read

Timeline

  1. 2026-11-14

    The authors publish the Auditable Authorization primary preprint reporting native banking continuations and other approval-chain audits.

Technical breakdown

  • Agno 3.1.12 executes native banking tools from a benchmark extension in cloned state.
  • Each banking family crosses four cases, two initial decisions and control/transition arms, giving 16 episodes per family in each provider protocol.
  • In state-change transitions, another authorized payment settles before continuation; all four originally approved GPT-6.1-Sol transition episodes still commit the now-invalid transfer.
  • In scope-revision transitions, four originally approved episodes execute the earlier confirmed transfer before revised continuation text is processed.
  • Two original reserve-breach continuations encounter provider failures only after effects occur; two terminate normally.
  • Risk-directed cases and repeated transitions diagnose mechanisms and do not estimate deployment prevalence.

Authorization boundary

Where the authorization boundary should have been

This incident is categorized as Governance bypass. The relevant Permission Protocol gate is Runtime Gate. The read is conditional: the block only applies where the real action boundary is routed through a gate.

If enforced at
Banking tool execution boundary immediately before transfer commitment
Still needs
PP does not itself establish trustworthy balances, propagate conversational withdrawal into authenticated revocation, repair runtime scheduling or guarantee completion of permitted work. Ungated tool paths remain outside coverage.
Receipt required for
The exact source account, recipient, amount and current conditional authority for each transfer

An independently integrated execution gate could require current action-bound authority and revalidate reserve conditions before transfer commitment.

Start small

Put the relevant gate at this action boundary.

This incident maps to Runtime Gate. Start with the boundary that controls the actual action, then require a signed receipt before execution.

Replay this incident with a signer in the loop