Only if someone authorized approves that exact change. An agent can read the order and the supplier’s message and prepare a proposal. A person with authority approves it, the approved process applies it, and someone checks the record.
It can read the supplier’s email, so why not update the order?
Permission to read an email is not permission to buy. A proposed replacement supplier still needs a decision.
1. Different steps, different permissions.
Read and prepare. Access the allowed order and message, and prepare a supported proposal.
Review. Check the supplier, item, quantity, price, delivery, budget and who is authorized to decide.
Apply. Make only the approved change, through the configured process, and record the result.
Practical check: Instructions are not a substitute for access controls.
A fictional example: the price changed.
- Approved
- 100 units at CAD $12 each, $1,200 in total.
- Revised
- 100 units at CAD $14 each, $1,400 in total.
- Check
- A $200 change is a different proposal. Apply the company’s reapproval rule before committing it.
2. Review the version that will actually change.
Show the previous value, the proposed value, the reason and the source beside the order and line. Before applying it, check whether someone else already changed the record or the supplier sent a newer reply. A conflicting or outdated proposal goes back to review.
Practical check: Approval should refer to the exact action being carried out.
3. A timeout is not a failed order.
If the connection drops after submitting, the update may or may not have reached the system. Check the record and the transaction reference before trying again, and use controls that prevent duplicates. Escalate an unknown result rather than risk a second order.
Practical check: Verify what happened, not only what the agent reported.
4. Make the limits enforceable.
For a first release, consider draft-only access and explicit approval for any change. Restrict the suppliers, records and actions it can touch. Treat instructions inside incoming documents as content, not authority. Name who handles exceptions and how to stop it.
Read more: Letting AI Update HR or Payroll Records: Approve Every Change First · AI Agent Permissions: What Can Your Agent See and Do?
These figures are fictional, not approval thresholds. This is a design brief, not a purchasing control framework.