TL;DR:

mureo v0.7.1 (released 2026-04-29) lets an AI agent analyze your real Google Ads and Meta Ads accounts from a local XLSX. No OAuth, no developer token, no SaaS login.

Mutation tools return {"status": "skipped_in_byod_readonly"} by construction. The agent can recommend a budget shift; it cannot execute one.

Read-only by construction is the structural answer to the threat model I wrote up here . This post is the walkthrough.

A couple of weeks ago I posted about the three failure modes of AI agents that touch ad accounts: prompt injection, credential exfiltration, and unbounded mutations. The honest conclusion was that "be careful with your refresh token" is not a serious answer when the LLM will eventually be tricked.

The structural answer is: don't connect the agent to the account at all. Drop a CSV. Let the agent reason over the numbers, write up the diagnosis, and propose changes you execute by hand if you trust them.

That mode shipped today as mureo v0.7.1.…