All docs
How it works

Forbidden Rules: limit what the agent can read and change

TL;DR

A Forbidden Rule stops the agent from reading, creating, editing or deleting what you name: a platform, an account, specific resources (campaigns, domains, properties, repos …), a kind of data, or a tool — for everyone or only some callers. Describe it in words, answer the questions the drafter asks, check the Allowed / Blocked examples, save it (it starts OFF) and turn it on. It holds on every path the agent can take.

What a rule is made of

  • Platform — Google Ads, Meta, Cloudflare, Google Analytics … or every platform.
  • Accounts — the connected accounts it covers (none picked = every account of those platforms).
  • Resources — specific campaigns, domains, properties, repos and more: Allow ONLY these (everything else of that kind is stopped) or Stop these (only those are stopped).
  • Actions — reading data, making changes (narrowed to creating or editing if you like) and deleting. Making changes covers deletes too.
  • Who — everyone, or only some roles (admins, editors, members) or callers (people in the app, schedules and agent loops, api keys (mcp / rest), connected apps (oauth)).
  • Data — a kind of data wherever it lives: audiences & customer lists, personal / customer data, conversions & tracking, budgets & bids, creatives & assets, reports & performance, billing & payments, account settings & users, email campaigns & flows, catalog & products.
  • Exceptions — what the rule lets through (a kind of data or a specific typed tool). An exception never lets a general gateway or raw request through: it could carry other changes too.

Write one in plain language

  1. 1Say WHAT to stop (reading, creating, editing, deleting), WHERE (a platform, an account, or specific campaigns / domains / properties / repos), and — if it matters — WHO (API keys, connected apps, schedules, a role).
  2. 2To allow only a few things, say “only”: “may only change DNS for a.com and b.com”. Everything else of that kind is then stopped.
  3. 3Review how the rule is understood and answer any questions — pick one, several, or “All accounts”.
  4. 4Check the example requests marked Allowed / Blocked, use “Test this rule” for your own case, then Save. A new rule is saved OFF.
  5. 5Turn it on from the list. It holds everywhere the agent works: tasks, schedules and loops, MCP, the REST API and raw requests.
Nothing is saved while you draft. A saved rule starts OFF, and it cannot be turned on while a question is still open or while it would block nothing.

Answering the questions

  • When a name matches several accounts, or none, the drafter asks which ones you meant. Pick one, several, or “All accounts” — picking “All” clears the others, and picking an account clears “All”.
  • “What should this rule stop?” lets you tick several: reading, changes, deletes — or “Everything”.
  • An allow-list with no platform asks which platforms it is for (one or several).
  • You can always add your own words, or choose “I will set the fields myself” and edit the form directly. Then click Draft again with my answers — answered questions are never asked again.

Examples you can copy

Paste one into Describe it in words on the Forbidden Rules page and adjust the names:

  • “The Cloudflare account may modify DNS records only for makingitcount.dev, feeltrulyalive.com and futureneverstops.com. Modifying DNS records for any other domain is prohibited.”
  • “On Google Ads, only campaigns 111 and 222 may be changed.”
  • “Never touch Google Analytics property 269416110.”
  • “The agent may only push to the GitHub repo octo/site.”
  • “No deletes anywhere.”
  • “API keys may not read customer data.”
  • “No new Meta campaigns — editing existing ones is fine.”
  • “No edits on Google Ads; creating new things is fine.”
  • “Never change budgets on Google Ads.”
  • “Don't read or change anything on TikTok.”

Test, turn on, turn off, delete

  • Example requests — the dialog shows sample calls for the rule's platforms marked Allowed or Blocked, judged by the same matcher the agent meets.
  • Test this rule — try your own call (platform, account, action, tool) before saving.
  • Turn on / off — the switch on each rule. A rule turned on reaches every server within a few seconds.
  • Edit / Duplicate / Delete — from the rule's row. Deleting a rule that is on lets the agent do what it forbade again.
  • Each rule shows how many calls it blocked in the last days, so you can see it working.

Where a rule is enforced

Every path the agent can take asks the same rules before anything is sent: tasks in the app (planned and autonomous), schedules and agent loops, project tasks, MCP (Claude, Codex, Cursor …), the REST API, raw platform requests, queued approvals when they run, dashboards and alerts that read data, and views. The same change sent through a platform's general tool or a raw request is judged as the tool it amounts to.

Resources each platform supports

PlatformResources a rule can name
AdobeReport suite, Property, Activity
Apple AdsCampaign, Ad group / ad set, Ad
AppLovinCampaign
BigQueryDataset, Table
ChatGPT AdsCampaign, Ad group / ad set, Ad
CloudflareDomain / zone, Worker, Bucket, Project
CM360Campaign, Ad
DV360Campaign, Insertion order, Line item
GitHubRepository, Branch
Google AdsCampaign, Ad group / ad set, Ad
Google AnalyticsProperty, Data stream
HubSpotCRM record, List
KlaviyoList, Segment, Campaign
LinkedIn AdsCampaign, Campaign group, Ad
Merchant CenterProduct, Data source
MetaCampaign, Ad group / ad set, Ad, Page
meta_pagesPage, Post
Microsoft AdsCampaign, Ad group / ad set, Ad
Organic socialPage, Post
Pinterest AdsCampaign, Ad group / ad set, Ad
Reddit AdsCampaign, Ad group / ad set, Ad
Search Ads 360Campaign, Ad group / ad set, Ad
Search ConsoleSearch Console site
ShopifyProduct, Collection, Discount
SHOPLINEProduct, Collection, Discount
Snapchat AdsCampaign, Ad group / ad set, Ad
Spotify AdsCampaign, Ad group / ad set, Ad
Tag ManagerTag Manager container, Tag Manager workspace
TikTokCampaign, Ad group / ad set, Ad
X AdsCampaign, Line item
No resource restriction on: Ad Manager, AdSense, AdMob, Microsoft Clarity, DataForSEO, Context.dev (web data & page monitors), Stripe, YouTube — their calls do not name a resource a rule could check. A rule there can still stop reading, changes or deletes on the whole platform or account; a rule that names resources there says it is not supported before you turn it on.

Troubleshooting

  • “Nothing was saved: your workspace switcher shows … but your session is still on another workspace” — the switcher and your session disagree (a switch made while the tab was in the background is not always saved). Click Use “<workspace>” on the page; it fixes the session and reloads. Older pages said only “not found” here.
  • “This rule is not in the workspace you are working in now” — the rule was deleted (in another tab or by someone else), or the list was loaded in another workspace. Reload the page.
  • The switch is greyed out — the rule still has an open question, or it blocks nothing as written (a tool that does not exist, a resource the platform cannot check). Edit it; the dialog says which.
  • A name was not found — a campaign or ad name the save could not look up is kept as typed and flagged; use the id, or save the rule again after the campaign exists.
  • Only an admin can change rules — every member can see them and what they blocked.

Frequently asked questions

Does a rule stop an approval that is already queued?
Yes. A queued change is judged again when it is about to run; a rule turned on in between stops it.
Can a rule allow only some domains or campaigns?
Yes — choose Allow ONLY these (or write “only …”). Calls on anything else of that kind are stopped, and a call whose target cannot be read is stopped too.
Do rules apply to my MCP and REST clients?
Yes. API keys and connected apps meet the same rules, and you can make a rule apply only to them (Who → API keys / Connected apps).

Related