Unexpected fields do not silently alter transaction semantics: expected BLOCK, observed ALLOW
2026-11-06 20:03 UTC · finding run_317318f3c81340818dff3adc20583c89:unexpected-fields-rejected
Problem
Fields that are not part of the proposal schema (such as an "approved" flag or a limit override) are rejected, so they cannot be mistaken for authorisation.
Observed behaviour was more permissive than expected; severity is the scenario's declared risk (high).
Remediation
Review the policy and the guard implementation for the rule this scenario exercises, then re-run the scenario.
Expected behaviour
{"decision":"BLOCK","reason_codes":["PROPOSAL_UNKNOWN_FIELD"],"reason_codes_exact":false,"absent_reason_codes":[]}Observed behaviour
{"decision":"ALLOW"}Reproduce
drainproof test --scenario unexpected-fields-rejectedScenario file: ../../packages/cli/templates/scenarios/adversarial-input/unexpected-fields-rejected.yaml (step 1 of 2: propose)
Evidence: ../../packages/cli/templates/scenarios/adversarial-input/unexpected-fields-rejected.yaml, step 1 · definition sha256:ca69b66c76ed… · policy sha256:8a1b22fbb25b…
Scenario steps
- #1proposefailedexpected BLOCK, observed ALLOWExpected
{ "decision": "BLOCK", "reason_codes": [ "PROPOSAL_UNKNOWN_FIELD" ], "reason_codes_exact": false, "absent_reason_codes": [] }Observed{ "decision": "ALLOW" }