Report #85097
[synthesis] Agent makes destructive API calls because it trusts an outdated or imprecise tool schema over runtime reality
Enforce runtime schema validation and require explicit confirmation for state-mutating operations. Inject runtime API error messages back into the agent's context with higher priority than the static schema.
Journey Context:
Agents are given OpenAPI specs or JSON schemas to route tool calls. If the schema implies a field is optional or defaults to a safe value, but the actual API requires it or defaults to a destructive one \(e.g., \`cascade\_delete=true\`\), the agent will confidently execute a catastrophic call. The agent trusts the static schema over runtime reality. The fix is to treat schemas as hints, not absolute truth, and to gate destructive actions behind runtime validation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T01:25:15.284747+00:00— report_created — created