How-to

Meta's ads MCP server rules: what a business portfolio lets an AI agent do, and what the rules do not cover

Since July 16, 2026 "anyone with full control of a business portfolio" can set rules for what AI agents may do on an ad account through Meta's ads MCP server. The rules are real and worth setting. They also leave three things open that matter most to an agency: creative defaults, per-account identity, and which client account an agent is in when one person reaches ten.

Adlio team5 min read

The short answer

Meta's ads MCP server rules exist since July 16, 2026. In Meta's words, they give "anyone with full control of a business portfolio the ability to govern what AI agents can do on their ad account, from budget changes to catalog updates." Set them. For an account where an assistant has write access, a blocked budget change is worth more than any prompt.

Then read what they are not. The rules we could see govern actions on account-level objects: campaigns, budgets, catalogs. They do not describe what a creative is created with (Advantage+ enhancements, music), what a new ad set's DSA advertiser and payer say, how ads are named, or which of an agency's client accounts the agent is in when the person who connected it reaches all of them. Those are the places a bulk launch goes wrong, and they need a rule layer of their own.

What Meta announced, in order

  • April 29, 2026. Meta ads AI connectors, open beta. "Meta's ads model context protocol (MCP) server and ads command line interface (CLI)" give "a secure, Meta-authenticated connection from their ad account to an AI agent." Capabilities: reporting, campaign management ("Create and edit ads, ad sets, and campaigns using natural language"), catalog management, signal diagnostics. "For MCP, no developer credentials, API setup, or coding required."
  • July 16, 2026. "You can now connect any AI application directly to Meta ads using your own developer app", and "ads MCP server rules, giving anyone with full control of a business portfolio the ability to govern what AI agents can do on their ad account, from budget changes to catalog updates."
  • October 6, 2026. Upload creative, preview ads, "Agent-staged work now lands as a draft in Ads Manager", and "Every action is gated behind advertiser-set permissions and explicit approval before anything goes live."

So the control model has three layers: the person's own Meta permissions (the agent cannot do what the person cannot), the portfolio's MCP rules (what the agent may do even where the person could), and the draft plus explicit approval before anything goes live. That is a reasonable design. The gaps are in what the middle layer can express.

What the rules cover, as far as we could read

We read the server's tool text in Claude on October 24, 2026. Rules we saw referenced: whether the agent may create campaigns, whether it may edit budgets, and a budget ceiling. Meta's announcement puts the range as budget changes to catalog updates. We did not find documentation listing every rule, and Meta's developer pages for the connector render only in a browser, so treat the list above as what we could observe, not as complete. If you have full control of a portfolio, the rules are in Business Suite; open them and read the actual options before relying on this article.

Three things the rules do not reach

1. Creative defaults. An Advantage+ enhancement is a property of the creative, set at creation. Meta's MCP exposes a master switch and an opt-in list; opting out per key is a JSON string the agent must send, and unsent keys get Meta's default (our August 2026 read-back: OPT_IN). No portfolio rule changes that. What an agent-built ad launches with has the table; the saved-preference article explains why an account preference does not reach API-created creatives.

2. Per-account identity. The ad set tool fills the DSA advertiser and payer from the ad account's business name. For an agency-run account that can be the wrong legal entity on a client's ad set, and the rules have no field for it. Meta ad account roles for agencies covers who can set what; the DSA detail is in the beneficiary and payer guide.

3. Which account the agent is in. Meta's connector authenticates the person. A media buyer with partner access to twelve client portfolios connects once and reaches twelve ad accounts. The rules are per portfolio, owned by whoever has full control of that portfolio, which for a client account is the client. The agent acts in whichever account the conversation names, and "the account we discussed yesterday" is a prompt, not a permission. How agencies get access to a client's ad account explains why full control is rarely the agency's.

What to set, and where

  • Meta's rules, per portfolio you control: block budget edits for agents unless a human is the one asking; set a ceiling; decide whether agents may create campaigns at all. Ask clients who own their portfolios to do the same.
  • Your own layer, per ad account: the enhancement policy (all off, written into every creative), the naming pattern, the UTM template, the DSA names, and who may launch into which account. These are not Meta rules; they are yours, and they need to live somewhere an agent cannot talk its way around.
  • A paused handover. Whatever the agent builds should exist as paused ads a person activates, not as live ads a person reverts. Draft vs paused vs in review explains why paused is the verifiable state.

How Adlio handles it

Adlio is the second layer. Team members log in by email and see only the ad accounts shared with them, with a launch right per account; nobody shares the owner's Facebook login. Settings per ad account hold the enhancement policy (default: explicit OPT_OUT on all 69 keys plus music off), the naming pattern, the UTM template and the DSA names, and Adlio writes them into every creative and ad set it creates. An assistant connected through Adlio's MCP (live since October 24, 2026, paid plans) acts as the person who connected it, inside those rules: it can fill the draft and ask for a preview, it cannot change Settings, budgets or activate anything, and launch_ads runs only with the previewToken of the exact draft the person saw and confirmed: true. Every ad lands paused; the activity feed records who launched, in which account, through which assistant. Start on bulk upload Facebook ads.

Frequently asked questions

Who can set Meta's ads MCP server rules?+

Meta, July 16, 2026: "anyone with full control of a business portfolio". For an agency that means the client, when the ad account sits in the client's portfolio and you have partner access; you can ask the client to set them, or to grant you full control, which is a bigger ask than the rules themselves.

What can the rules block?+

Meta's announcement names the range: "from budget changes to catalog updates". In the server's own tool text, read on October 24, 2026, we saw rules for creating campaigns and editing budgets (allowed or blocked) and a budget ceiling. We have not seen a rule for creative enhancements, naming, UTM parameters or DSA fields.

Do the rules control Advantage+ creative enhancements?+

Not that we could find. Enhancements are stored per creative in degrees_of_freedom_spec and are set by whatever creates the creative. A rule that blocks budget changes does nothing about a creative created with Meta's defaults. Enforce enhancements where the creative is made.

An agency with ten client accounts: one connector or ten?+

Meta's connector authenticates a person, and that person's access spans every account they can reach. The rules are per portfolio, set by whoever has full control of it. So in practice: one connection, ten portfolios, ten rule sets owned by ten clients, and the agent in whichever account the conversation names. The safer design for volume is a layer that holds per-account rules and launch rights of its own; see the article for how Adlio does that.

Sources

Adlio team

Built by media buyers who launch Meta ads in volume. Questions or corrections: support@adlio.ai.

Topic cluster

Agentic ads, safely

Launching Meta ads from Claude or ChatGPT: what an agent leaves switched on, and how to keep control.

Start here

Meta's ads MCP vs a bulk uploader: what each one leaves switched on

Related guides