Access policy edits take up to 30s to reach the tool gateway, so a new forbid does not stop tool calls started meanwhile #1263
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#1263
Reference in new issue
Block a user
Same bug class as archie-core-i0scw, on a hotter path. archiegateway builds its tool authorizer with infraaccess.StartLive + applystatus.RestampInterval (internal/app/archiegateway/tools.go:110), and that authorizer is consulted on every tool call (internal/gateway/tool_access.go:27), not per task. So a forbid on an identity can be bypassed for up to 30s by a tool call inside a run that started before the edit, and a tool call is the commonest mutating action there is.
Done when a policy edit is enforced by the tool gateway for any tool call dispatched after the edit returns, by the same mechanism chosen for i0scw (do not add a second one).
Close reason
Same mechanism: archiegateway's tool authorizer is a Live chain, so a guarded tool call now re-reads the revision before deciding (internal/app/archiegateway/tools.go:110).
Imported from beads
archie-core-cf5mz· GitHub #1841 · type bug · priority P2 · created 2026-10-25 · closed 2026-10-25