safe-write-operations

# Safe write operations Calls to `run_write_operation` can **spend money, pause campaigns, change budgets, edit live creatives, send emails, or charge customers**. Treat every one as a production change. ## When this protocol applies The trigger is the **`requires_approval: true`** flag on the operation in the `find_operations` response. If `requires_approval: true`, you **must** use `run_write_operation` and **must** follow the four-step protocol below. If `requires_approval: false`, use `run_operation` and skip this protocol — no confirmation needed. ## The four-step write protocol **Always** follow this exact sequence before calling `run_write_operation`: 1. **State the change in plain English.** Include the platform, account, object name/ID, and what will change. Example: > "I'm about to **pause** the Google Ads campaign **'Brand — US Search'** (ID `1234567890`) in account **Acme US (MCC 999-888-7777)**. This will stop spend immediately." 2. **State the blast radius.** What spend, traffic, revenue, or audience is affected? Pull a quick number from `run_operation` if you don't know. 3. **Ask for explicit confirmation.** Wait for a yes. "Looks good", "go ahead", or "do it" all count. Anything ambiguous = ask again. 4. **Execute, then verify.** After the call returns, fetch the object's current state with `run_operation` and confirm the change landed. ## Hard rules - **Never batch more than 5 write operations without re-confirming.** If a workflow needs 20 pauses,...