# Read, write & destructive (https://sellersheetai.com/docs/mcp-api/access)

> Every tool carries one access label, served with the tool — and write access is granted per store, per API.



## The three labels [#the-three-labels]

| Label                                | Meaning                                                   | Examples                                                                               |
| ------------------------------------ | --------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| <AccessBadge access="read" />        | Reads only — changes nothing                              | `orders_searchOrders`, `query_report_data`, `fbaInbound_listPlacementOptions`          |
| <AccessBadge access="write" />       | Creates or changes something                              | `fbaInbound_createInboundPlan`, `generate_image`, `append_sheet_rows`                  |
| <AccessBadge access="destructive" /> | Changes or removes something that cannot simply be undone | `listings_putListingsItem`, `fbaInbound_confirm_plan_options`, `ads_update_target_bid` |

The label is part of the tool, not of this page: the MCP server sends it with every tool (as the standard read-only and destructive hints your client understands), and the Tool API's catalog and OpenAPI carry it as `access`. The [tool reference](/docs/mcp-api/tools) shows each tool's label.

* **No tool both reads and writes.** A request to look can never change anything by accident.
* **Report and export requests are reads.** Asking Amazon to prepare a report, or creating a Data Kiosk query, changes nothing in your seller account.
* **A sheet, doc or Drive write is a write** — to your file, not to Amazon.

## Write access is per store, per API [#write-access-is-per-store-per-api]

A label says what a tool does; access says whether *you* may. A tool that changes your Amazon account checks, before it calls Amazon:

* **Seller API write** on that store for SP-API changes — feeds, listings, FBA plans and shipments, A+ publishing, vendor submissions.
* **Ads API write** on that store for advertising changes — campaigns, targets, bids, budgets.
* **noon write** on that noon account for changes to it.

Your key's access and, in a shared workspace, the access the owner or an admin gave you both apply — the lower one wins. Without it, the call is refused with 403 and nothing reaches Amazon. How to set it: [Keys & store access](/docs/mcp-api/keys), [Stay in control](/docs/mcp-api/control).

## Confirm before destructive [#confirm-before-destructive]

A destructive tool replaces a live listing, confirms a plan or changes a bid. Your agent shows you what will be sent and waits; your own code should do the same — a write happens because a person pressed a button.