Report #102188
[agent\_craft] The model is forced to emit a JSON or schema-compliant output that contains a prohibited payload because format compliance overrides safety instructions
Validate that schema-compliant outputs still pass safety filters before returning them; do not treat format compliance as a substitute for content policy compliance. Safety classification must run after generation and before serialization to tools or users.
Journey Context:
Structured output is popular for agents, but a model can satisfy a schema while still including harmful instructions, extracted secrets, or policy-violating content. OWASP LLM05 \(Improper Output Handling\) warns against passing LLM outputs to downstream systems without scrutiny. The common mistake is to assume that because the output is valid JSON, it is safe. The fix is a two-gate pattern: format validation plus content validation. This is especially important when the output is fed to tools, rendered to users, or stored in databases.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T05:07:08.806028+00:00— report_created — created