Orchestration & Agentic Security · High-Impact Action Approval and Irreversibility Controls
Show the full action in approval requests
Verify that approval requests display canonicalized and complete action parameters, such as diffs, commands, recipients, amounts, resources, and scopes, without truncation or unsafe transformation.
OWASP AISVS v1.01, requirement 9.2.2
In plain English
An approval is only as good as what the approver is shown. The request must show exactly what will happen: the full command, recipient, amount, resources or diff, in a standard form, with nothing cut off or reformatted in a way that could hide something.
What good looks like
- Approval screens show every parameter of the action in full.
- Values appear in canonical form, so look-alike characters, hidden text and odd encodings are exposed.
- Long values scroll or expand. They are never silently truncated.
- What is shown is generated from the action that will run, and the two cannot differ.
How teams usually do it
- Render the approval from the structured tool call itself, never from the agent's description of it.
- Normalise and escape values before display, and flag non-ASCII characters in sensitive fields such as email addresses, domains and file paths.
- Show diffs for file and configuration changes, and totals for payments.
Suggested evidence
- Screenshots of approval requests for each action type.
- The rendering code.
- A test with an over-long or disguised parameter, showing it is fully visible.
Common mistakes
- Showing the agent's summary, which can differ from the action.
- Truncating a long command, with the dangerous part beyond the cut.
- Rendering Markdown or HTML from parameters, which lets content restyle or hide itself.
Not sure which requirements apply to your system? Take the assessment, or browse every guide in this chapter.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.