Will Claude Code change my prices or send emails without asking?

By Stef · 28 October 2026

No: Claude Code does only what its written rules and its keys allow, and a good setup makes it ask first. In the MOGA workspace it asks before anything with money in it (prices, spending, a profit below your lowest), anything sent in your name, anything it had to guess and anything that cannot be undone. It acts alone only on a value it found in your own pages or data, when the change can be undone, such as a draft, a label or a note, and then it tells you. Everything that needs you waits as one row on a decision page, for your Go or Skip.

This page is for the owner who likes the idea of Claude doing the checking but does not want a surprise on a product page or in a customer's inbox. The examples come from sample sessions for invented businesses. Jump to the free sample page.

What does it do on its own?

It acts alone only when the value is FOUND in your own pages or data and the change can be undone. That means a draft, a label, a note or a read only check. It then tells you what it did. Every value Claude fills in shows how sure it was: FOUND means read from your own pages or data, ESTIMATE means a guess to check, NOT FOUND means nothing shows it and Claude asks you.

What does it always ask first?

It asks first for money, for anything sent in your name, for guesses and for anything it cannot undo. In practice:

• Prices and spending. A price change waits for your Go, and so does anything that would take a profit below your lowest. In a sample session the answer reads: “Yes. Margin after the discount is 35 percent, above your 32 percent floor.” You then click Go on the price change.
• Mails in your name. Claude writes a draft reply to a customer or a chase mail to a supplier. You read it and press send.
• Guesses. Anything marked ESTIMATE or NOT FOUND comes back to you as a question.
• Live product pages. Changes to them wait for your Go as well.

What actually stops a mistake?

Two layers: keys that can only read, and rules written in the folder. Each connection to your sales platform is set up with a read only key wherever the tool offers one, so Claude can read orders and stock but cannot change them. That one is a lock. The ask first list in the workspace is a rule: Claude follows it because it reads it at the start of every session, and a rule is not a lock. That is why the setup uses both.

One plain fact from the setup page: in the mode it recommends, the editor's own pop ups are off, so the read only keys and the written rules carry the weight. Where a tool offers no read only key, the rule is all you have, and that connection deserves extra care.

How do I test it in 10 minutes?

Ask for the two risky things and check that neither one happens.

1. Ask Claude to lower the price of one sample product. You should get a row waiting for your Go, and the price should not move.
2. Paste a sample customer message and ask for a reply. You should get a draft, and nothing should be sent.
3. Open the ask first rules in your folder and read them once. If a rule is missing, add it in plain words.

Where does this stop?

It cannot protect you from a Go you give too fast. The decision stays yours, so read the row before you click. It also does not run while you sleep: it works in a session you open.

Related questions

• How does Claude Code work with a Trello board?
• Do I need to code to use Claude Code for my online business?
• Claude for a small business: the 5 jobs it takes off an online seller
• One Trello board for stock, supplier orders and returns

MOGA World is independent and not affiliated with Anthropic or Atlassian. Sample businesses and numbers on this page are invented. Questions: stef@mogaworld.co