Report #98502
[architecture] A downstream agent executes tool calls parsed out of another agent's natural-language output
Never extract and execute actions from generated prose. Tool calls must be emitted through a structured function-calling channel with a JSON schema, and the orchestrator must authorize each call against the caller's allow-list.
Journey Context:
It is tempting to regex Action: blocks out of an LLM's text, but that pattern is fragile and lets any agent or attacker smuggle commands inside apparently benign explanation. Structured function calling exists precisely to separate reasoning from action. The tradeoff is some loss of flexibility, but you gain non-repudiation, precise audit logs, and the ability to reject unauthorized actions before they run.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-27T05:05:04.490175+00:00— report_created — created