Access & permissions
Every tool call is checked three ways before it runs: who you are, what level you have, and which brand + marketplace you are asking about. Whatever app you connect gets exactly your permissions — never more.
Access levels
| Level | Can do | Cannot do |
|---|---|---|
| View-only | Read and analyze everything in scope: performance, search terms, keywords, budgets, change history, reports. | Change anything on Amazon. Every write tool is refused. |
| Can edit | Everything above, plus stage and push changes: bids, budgets, status, placements, new campaigns. | Reach brands or marketplaces outside their scope. |
Brand & marketplace scoping
An admin grants either all clients or a specific list, and per client either all marketplaces or specific ones (US, UK, IN, CA, AE, SA, AU, MX…). Asking about anything outside that scope returns a denial, not data. You can see your own scope on your dashboard overview.
OAuth scopes
| Scope | Meaning |
|---|---|
| mcp:tools | Call MCP tools as the signed-in user. |
| mcp:read | Read data through MCP tools. |
| offline_access | Stay connected with a rotating refresh token — no daily re-login. |
ⓘ
OAuth scopes get an app in the door; your per-user level and client/marketplace grants decide what actually runs. The narrower of the two always wins.
Who controls what
- You — connect and disconnect your own apps (My connections), change your password, request no-logout.
- Admins — approve accounts, set levels and scopes, revoke sessions and apps instantly, grant no-logout, deactivate accounts.
- The server — logs every call with your name, tool, client and marketplace; denials are logged too.
Write safety
Write tools are the small minority — see the WRITE pills in the tool reference. Changes are staged first where possible, every push is recorded in the change history, and an admin can see today's changes at any time.