Blocking dangerous agent actions in prod — streaming is the guardrail blind spot
dank_as_fuck_ · reddit · 2026-09-27
The poster (founder of axonpush, disclosed) asks the community: once an agent holds real tool access (payments, CRMs, EHRs, databases), the risk is no longer a bad answer but a bad action — an oversized refund, a write to the wrong record, a tool it shouldn't touch. Most setups just log and review after the fact; he's polling whether people use hard checks inside tool functions, guardrails libraries, or human approval for risky actions.
He shares an honest engineering caveat: axonpush sits inline on OpenAI/Anthropic calls and can block a tool call by name or argument (e.g., amount > 1000) before execution, but this only works on non-streaming responses — with streaming, the tool call reaches your app before the full call is known, so it can only be flagged after the fact. He's also curious whether teams stream agent responses in prod or disable streaming for tool-heavy steps.
More from coding & agent
- Claude dumped 177GB of temp files in a day and filled a user's disk — kevinkern · 2026-09-27
- SafeScript: a Turing-incomplete JS subset lets agent policies replace code review — uriwa · 2026-09-27
- Open source AI-SQL engine Quail signals shift toward cheap task-specific models — sh_reya · 2026-09-27
- Life hack: run Claude Code with --dangerously-skip-permissions at / to free disk space — Kuprel · 2026-09-27
- Bend: a language that blocks AI coding mistakes with Lean-style proofs at C speed — arthurcolle · 2026-09-27
- Claude generates 177GB of temp files in a day, fills developer's entire disk — banteg · 2026-09-27