Being recognized isn’t the same as being authorized
The distinction is easy to miss. A store can know which agent is calling without giving it access to an account. And a customer can approve access for one job without approving every action the store offers. The commerce extension spells out the division: Poppy helps the agent arrive and establish identity; the Universal Commerce Protocol describes the shopping tools the store makes available. The extension names a permission for reading orders. That is not a promise that every storefront offers the same tools, or that putting a discovery file online makes those tools safe.
For a store trying this out, start with one test order in a sandbox before trying to automate the whole support queue. Ask the agent for the shipment status. Then ask it to change the address. The first request should give a useful answer with read-only access. For the second, a store could send the customer to a confirmation screen or to support, depending on its policy. And if the parcel has already left the warehouse, the agent should say the address can’t be changed through that route, not imply the edit went through.
The best outcome of that test isn’t that the agent does everything. It’s that it gives the customer a tracking update without turning a simple question into permission to edit the order.