A decision on a held MCP call can say why it overrides AtmanID's suggestion; a later version will require the reason fields.
- AddedPOST /api/v1/mcp/authorize/holds/{id}/decision — New in 1.42.0: an optional
category, the reason for a decision that goes against AtmanID's suggestion (approving a HIGH or CRITICAL hold, or denying a MEDIUM or LOW one), with the values the console offers; the audit record carries it asnew_state.override_category, as a console decision does, and an unknown value is 400 VALIDATION_ERROR naming the field. Nothing changes for a request without it, and nothing is refused today. In a later version, announced with its date before it takes effect, a decision on a HIGH or CRITICAL hold will requirenote, and a decision against the suggestion will requirecategory. To be ready now, sendnotewith every decision andcategorywith every approve: gateway holds are created at HIGH risk. Until then the audit record of a decision without them carriesnew_state.reason_rule(modeapi_key_exempt) naming what was missing, so you can find the calls to change.