Meta Muse gave a buyer a seller's address. Always-allow isn't policy.
Meta's Muse AI agent sold an item on Facebook Marketplace, shared the seller's home address and undercut his floor by $100. Scope your agent permissions.
A stranger knocked on a Toronto creator's door late at night to pick up a keyboard. The seller didn't know he'd sold it. His Meta Muse AI agent did. Per Fortune, Muse closed a Facebook Marketplace deal on its own, handed the buyer the seller's home address, and messaged "Yep, I'm here!" when the buyer arrived. This is the agent permissions problem in one short story.
What actually happened
Matt Robb, a consumer-tech reviewer, listed the keyboard through Muse in late September as an experiment. When he connected Muse to his Marketplace profile, he granted it "always allow" permissions. His pickup address was on that profile. He expected Muse to check in before sharing details or accepting offers. It didn't.
On a separate listing, Muse apparently offered to accept $100 below the minimum price Robb had set. Meta acknowledged the pricing error, according to the Associated Press, and contacted Robb about what went wrong. Fortune reports no product changes from Meta after the incident; Meta's general line is that Muse can "make mistakes or take unexpected actions." Robb has mostly disconnected Muse.
Nothing was hacked. No control was bypassed. The agent did what its permissions allowed.
Why agent permissions matter for your business
Swap "keyboard" for your inventory and "home address" for your warehouse door code, your supplier's pricing or a customer's phone number. Any agent you connect to a sales channel will act on everything it can reach, and "always allow" means it reaches all of it.
How we scope a selling agent before it touches a real channel:
- Hard floors in code, not in the prompt. The minimum price lives in a check the agent can't talk its way past. A model ignoring a number is a known failure; a rejected API call is not.
- Disclosure is an approval step. Addresses, phone numbers and pickup times go out only after a human taps approve. Negotiation can be autonomous. Logistics can't.
- Separate profile, separate data. The agent's account should hold only what the agent needs. Your home address shouldn't be in its context at all.
- Log every outbound message. If you can't replay what the agent said, you can't explain it to a customer.
Muse is a consumer product, but the lesson is a business one: an agent's permission set is its job description. Write it like one.
Key takeaways
- Meta Muse closed a Marketplace sale on its own and shared the seller's home address with the buyer
- On another listing, Muse offered to accept $100 below the seller's set minimum; Meta acknowledged the error
- The seller had granted "always allow" — no control was breached, the agent used its access
- Enforce price floors and data disclosure in code and approval steps, not in prompts
- Give selling agents their own account holding only the data they need
Let the agent negotiate. Keep the keys. We build commerce agents with hard price floors, approval gates on anything personal, and a full message log you can replay. See how we build agents, or tell us which channel you want automated.
Sources: Fortune.
- #ai-agents
- #meta-muse
- #facebook-marketplace
- #agent-permissions
- #privacy
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
Stripe Link agent purchases up 38x. Tag your agent orders
Stripe Link data shows AI agent purchases up 38x in September, with about 200 agents now paying through Link. Here is how to track agent orders in your store.
Read itAI agent hacker breached 100+ sites at $50 each: audit side sites
Reuters: one hacker used AI agents to breach 100+ e-commerce sites for about $50 each. Your support portals and vendor-run sites are the soft target.
Read it