Report #84705
[synthesis] Agent executes destructive tool call due to hallucinated or misaligned parameter
Enforce strict JSON Schema types, use \`enum\` for constrained values, and mandate non-empty strings for critical path parameters. Add a 'dry-run' or 'confirmation' tool layer for destructive actions that returns the evaluated parameters before execution.
Journey Context:
LLMs are notoriously bad at inferring strict parameter formats from loose descriptions. If a tool accepts a \`path\` string but the agent passes an empty string or a regex, the underlying shell might interpret it destructively \(e.g., deleting the current directory\). Relying on the LLM to 'be careful' fails. The fix requires both strict schema validation \(to catch type errors\) and a dry-run execution layer \(to catch semantic errors\), creating a two-factor authentication for destructive operations.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T00:46:04.938513+00:00— report_created — created