AI Store Permissions and Approval Controls
Permission, store scope, plan entitlement, provider support and browser approval are five separate checks.
Access presets
View only grants read. Manage stores grants read and write. Full access adds sensitive permission. Each client grant and API key also has its own store scope; access to one store does not authorize another.
Ordinary supported listing, media, stock and fulfillment writes do not each trigger Store MCP browser approval. Keep the AI client’s review controls enabled and review exact values before execution.
Owner approval
orders.cancel, orders.refund and stores.disconnect need sensitive permission and approval of the exact request by the workspace owner in Store MCP. Requests expire after 15 minutes. An assistant saying “confirmed” is not approval. Re-submit with the returned approvalId and unchanged arguments and idempotencyKey after browser approval.
An approval cannot add a missing capability or paid entitlement. eBay, Square and WooCommerce do not expose order writes in this release. Refused unsupported actions are not made available by upgrading.
Buyer details
orders.list excludes buyer details. orders.get requires both includeBuyer: true and sensitive permission, plus provider access. Sensitive reads do not themselves require the separate browser approval used for refunds. Do not request buyer details for a catalog or stock task.