Separate preparation from execution

In the connected-request walkthrough, classifying a request and gathering context come before a tool changes a record. Keeping these steps separate gives the application a place to validate the proposal.

Show what a person is approving

An approval should identify the intended action, its target, and the relevant evidence. A generic confirmation button is insufficient if the person cannot see what will change.

Test the refusal path

Include requests with missing context, invalid targets, and actions outside the allowed scope. Stopping should be an expected outcome that the interface explains, with a clear owner for the exception.

Carry the decision into the record

Record the proposal, authorization, and execution outcome together. An approval does not by itself prove that an integration succeeded; failed and duplicate actions still need handling.

Explore the workflow

Follow the connected-request walkthrough to see where validation and authorization fit.

Further reading

NIST AI Risk Management Framework covers evaluation and operational risk. OWASP’s prompt injection guidance explains untrusted inputs and permission boundaries.

An AIS Lab editorial perspective. Architecture and operating choices depend on the requirements of each application.