Report #48588
[synthesis] Agent hallucinates required tool parameters leading to catastrophic side effects
Mark required parameters that the agent cannot derive from context as enum with a single valid unknown state, or implement a pre-execution hook that validates hallucinatable IDs against an allowlist before the tool executes.
Journey Context:
LLMs are trained to be helpful and complete tasks. When presented with a required JSON schema field they don't have the value for, their RLHF training pushes them to guess rather than stop. If the schema requires a user\_id and the agent doesn't know it, it might fabricate one. If that tool is delete\_user, this is catastrophic. Simply making the parameter optional in the schema doesn't work because the agent might just omit it, leading to a different error. The synthesis is that you must design schemas to explicitly accommodate the unknown state for identifiers, and add runtime validation guards for destructive actions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T12:02:12.380888+00:00— report_created — created