A padlock locking a black metal gate in a chain-link fence, in black and white

Account bans

Can connecting Claude or another AI agent to my Meta ad account get it banned?

By The Tofu team ·

Connecting an agent through an official route doesn't break Meta's or Google's rules on its own. Use Meta's ads MCP server if you want Claude or ChatGPT in your Meta account; use Google's read-only MCP server, or the Google Ads API through your own Cloud project, for Google. Avoid browser bots and unofficial proxies. Accounts get restricted for what happens through the connection: ads that break policy, rejected ads sent again, or access that looks like a compromise. Start read-only, grant the narrowest permissions, and approve every change yourself.

As of October 2026.

Quick answer by situation

If you…UseWhy
Want Claude or ChatGPT to read Meta reportingMeta's ads MCP server, limited to reading by agent rules (or ads_read on your own token)Meta's own route; its terms bar automated access without its permission
Want an agent to build or edit Meta campaignsMeta's ads MCP server with ads_management, agent rules, and your OK before anything goes liveMeta says its write tools create items paused and your AI client asks before activating
Want an agent to read Google AdsGoogle's Google Ads MCP server, run with your own Google Cloud projectRead-only by design
Want an agent to change Google AdsThe Google Ads API through your own Cloud project, or a vendor tool you sign in to with your own Google accountGoogle bans "programmatic proxies," including hosted MCP servers that just re-expose its API
Are thinking of a browser agent that clicks through Ads Manager for youDon't, for ad accountsIt isn't an official API route, and the risk is yours
Already have a restricted or suspended accountThe platform's review or appeal, not a new accountBoth bar new accounts used to get around enforcement

What do Meta and Google actually say about AI agents?

Neither bans AI agents by name. Their rules cover how you connect and what the connection does. One post on Reddit's r/ClaudeAI, titled "Claude Code got my Meta ads account permanently banned," blames Claude Code for its author's lost account. That is a single report we couldn't verify, and it can't tell you why Meta acted. Here is what the platforms' own pages say.

Meta

  • Automated access. Meta's Terms of Service say: "You may not access or collect data from our Products using automated means (without our prior permission)." The Marketing API and the ads MCP server are Meta's own documented routes for programmatic access.
  • Responsibility. Meta is updating its Commercial Terms. Its US English page says the update takes effect November 20, 2026; its UK English page says 30 October 2026. The new terms add: "You are solely responsible for the acts or omissions of any third-party software or service that you use or authorize."
  • Ad review. Meta's review "relies primarily on automated tools." If a violation is found, "the ad will be rejected, and the Business Account or its assets may be restricted." Helping anyone "evade or circumvent our enforcement" is also prohibited.
  • Your own app. If you connect through your own Meta app, Meta's Platform Terms let Meta act "with or without notice," up to "suspending or permanently removing your App(s) and account."
  • Rate limits. An ad set's budget can change 4 times per hour through the API, and by default one object can be edited once every 30 seconds. When an ad account "generate[s] a large amount of abnormal traffic," Meta "will temporarily reduce the API Rate Limit quota." These are throttles, not bans, but Meta tells you to find what's causing the excess calls.

Google

  • Automation is allowed. Google's Developer Policies say they don't restrict "your own use of the Google Ads API in a programmatic or automated way," or open-source tools that end users download and connect "using their own access credentials."
  • Proxies are not. Under the updated Developer Policies Google announced on August 31, 2026, hosted wrappers are banned, including any "MCP server, proxy endpoint, or any similar service that solely replicates, wraps, or re-exposes Google Ads programmatic capabilities." End users "will need to manually sign in to make changes." Breaking this can cost the developer fees, downgraded access or "termination of your Google Ads programmatic access."
  • API terms. Use only documented means, don't "misrepresent or mask your identity," and don't try to exceed quotas. Google "may suspend or terminate your access to the Google Ads API" for "any or no reason."
  • Account suspensions. "Egregious" violations, including Circumventing systems, mean suspension "immediately without prior warning." If Google detects an unauthorized user trying to get in, it temporarily suspends the account "to protect against unauthorized charges."

If you want Claude or ChatGPT to read your Meta ads data

Use Meta's ads MCP server at https://mcp.facebook.com/ads. Meta says it "works with any MCP-compatible AI agent," and you don't need to own a Meta app. To keep it read-only:

  • Set agent rules, if they're available on your ad account. Meta's developer blog says rules "define the actions an AI agent can and cannot take on a given ad account or catalog." Its example: grant "read access to performance data" while "withholding the ability to make changes to budgets, campaigns, or creative." Meta suggests starting "in a read-only or approval-required posture."
  • If you connect with your own Meta app or token, grant ads_mcp_management plus ads_read, not ads_management. Meta requires one of the two, and ads_management gives the agent more tools.
  • With a system user token, only Employee-role tokens work. Admin-role system user tokens can't reach the server.

So is Meta's official MCP safe? It's Meta's own route, with scopes and rules that limit what an agent can do. That makes it lower-risk than an unofficial tool, not risk-free: Meta still reviews every ad the agent writes, and you're responsible for what runs. For setup, see connecting Claude or ChatGPT to ad accounts.

If you want an AI agent to make changes in Meta

Grant ads_management only once you trust the setup, and keep a person between the agent and live spend:

  • Paused by default. Meta says its write tools "create entities in a paused state; your AI client asks for confirmation before activation." The activate tool "starts spending budget," so read that confirmation every time. Edits to existing campaigns, ad sets and ads use a separate update tool, so check those too.
  • Rules. Use agent rules to block what the agent shouldn't touch, such as budgets.
  • Pace. Ask the agent to batch changes and stop on errors. Meta's advice for throttling errors is to spread requests out and back off before retrying.
  • Audit. The server's activity log tool mirrors the campaign history in Ads Manager.

If you want an AI agent to read your Google Ads data

Use the Google Ads MCP server from Google's API documentation. Google says it "is strictly read-only. It cannot modify bids, pause campaigns, or create new assets." You run it yourself, locally or on Cloud Run, with your own Google Cloud project at Explorer, Basic or Standard access.

For any other tool, give the Google account it uses the Read-only access level in Google Ads. Read-only users can view campaigns and run reports but can't edit campaigns.

If you want an AI agent to change Google Ads campaigns

Google's MCP server can't, so you have two routes:

  1. Your own API access. Call the Google Ads API from your own Google Cloud project, for example with an AI coding tool writing the code. Google's policy allows your own automated use.
  2. A vendor tool. Ask how it connects. A tool you use through its own app should have you sign in with your own Google account before it changes anything. A hosted MCP server or API that gives your AI assistant programmatic access through the vendor's Google access is what Google calls a programmatic proxy. Google says agencies and advertisers using programmatic access need "their own Google Cloud Platform account and Google Ads access."

Google enforces quotas with errors: Explorer access allows 2,880 API operations per day against production accounts and Basic 15,000, and going over returns RESOURCE_EXHAUSTED. Its API terms also say not to try to exceed them. To see what an agent did, open change history; API changes may show "Google Ads API" or the tool's name in the User column.

If you're thinking about a browser agent that clicks through Ads Manager

Agents that sign in as you and click through Ads Manager or Google Ads use neither platform's API, and Meta's terms bar automated access without its permission. Sharing your login with a tool is also a security risk: Google temporarily suspends accounts when it detects unauthorized access. Use the official servers instead.

If your account is already restricted or suspended

  • Meta. If you think an ad was rejected or your Business Account or its assets were restricted by mistake, Meta's Advertising Standards say "you can request a review of either decision in Account Quality." Don't open new accounts to get around it: Meta's Inauthentic Behavior policy bars using "inauthentic assets - including business manager accounts - to evade enforcement."
  • Google. In Google Ads, select the Contact Us link in the notification at the top of the screen to open the appeal form. You have at least 6 months from the suspension. Send one appeal at a time: if Google sees misuse of appeals, it pauses processing "for 7 days." Accounts are "only reinstated in compelling circumstances," and related accounts, or new ones you try to create, may be suspended too. Google's Circumventing systems policy lists "creating new accounts to re-enter the system" after a suspension as an example.
  • A compromise. Report it to Google Ads. When Google secures an account, it pauses only the campaigns the unauthorized user created or changed.

Before you appeal, revoke the agent's access, check the activity log or change history, and fix anything that broke policy.

What to avoid

  • Write access on day one. Run read-only for a few weeks and check the agent's answers against the platforms' own reports.
  • Admin rights for the agent. In Google Ads, only Admin users can give account access and change access levels; Standard users can still edit campaigns.
  • Loops on rejected ads. Google's Circumventing systems policy gives "creating variations of ads, domains or content that have been disapproved" as an example. Don't let an agent rewrite and resubmit rejected ads on its own.
  • Unattended runs. Meta's Ads CLI has --no-input and --force flags "for unattended operation." Keep them away from live accounts.
  • Exposed tokens. Meta's Platform Terms say to protect access tokens and app secrets. Keep them out of shared files and repos.

Where Tofu fits

Tofu Ads Agent (our product) is an AI agent that plans, builds, launches and optimizes paid programs on LinkedIn, Google and Meta, connected to your own ad accounts. Campaigns it builds are staged in your account switched off and never launch automatically; a person turns them on. Its weekly bid, budget and creative recommendations stay proposals until you approve them. That is the human approval step this page recommends, but it doesn't change Meta's or Google's rules: ads still go through their review, you're still responsible for what runs, and Tofu can't promise an account won't be restricted.

Sources

Related answers

More on

Let an agent build your next campaign.

Tofu Ads Agent reads your CRM, plans the funnel, builds the audience and creative, and stages full campaigns across LinkedIn, Google and Meta for your approval.

Try it free Get a demo