Approval-gated writes
AdCopilot reads freely and proposes each change first. Approval is your AI client's own permission prompt, backed by limits on AdCopilot's server.
AdCopilot draws a line between reading your accounts and changing them. Reading is free, and each change is proposed first.
How a change happens
- You ask, or the assistant finds something worth changing.
- It proposes the exact change in plain words: the account, the campaign, ad group, keyword or ad, the change, and what it expects to happen. Money is spelled out, daily with its monthly equivalent.
- You say yes. Where your AI client is set to ask before AdCopilot's write tools, it then asks permission to run the tool, and you allow it.
- It reports what changed and how to undo it, which is almost always the opposite call.
For example:
Add negative keyword "free" (phrase match) to campaign "Invoicing — Search". It blocks searches containing "free", which drove $60 of zero-conversion clicks last month. Tool:
add_negative_keywords.
Who does the approving
AdCopilot proposes each change first. For a hard stop, set your AI client to ask before AdCopilot's write tools: Needs approval in Claude; in Cursor, set the run mode to Allowlist and keep them off the allowlist (Cursor's cloud agents never ask). The approval is your client's own tool-permission prompt, not a screen AdCopilot shows.
If you tell your client to always allow a tool, it will run that tool without asking again. That is why the limits that matter hold on AdCopilot's server, whatever the client does:
- It cannot delete. See It can never delete.
- It cannot publish a Tag Manager container. Its tag changes wait in a workspace for you to publish.
- It builds every campaign paused. A build that asks to start switched on is refused, and nothing in it runs.
- It will not switch on a campaign it built for you. That switch is yours, in Google Ads.
- It asks for your budget before it builds, and refuses spending past your monthly cap. See The budget checks.
- It only reaches the accounts you switched on, within what your Google sign-in, or a teammate's login shared with you, can open. A Google Ads change always runs on your own login: a shared login reads Google Ads, and changes only Analytics, Tag Manager or Search Console.
In Claude Code (version 2.1.214 or later), one tool is different:
set_campaign_status, which pauses or switches on a campaign that already
exists. It is the only tool that changes an existing campaign's status
(update_campaign refuses a status). It always brings up Claude Code's
permission prompt, even if you set it to always allow, and a run with nobody
there to answer cannot use it.
In Cursor, there is no Needs approval setting. Its run mode decides: in Allowlist mode a tool that is not on the allowlist stops for you, so keep AdCopilot's write tools off it. Auto-review, Cursor's default, can let a write run without asking, Run Everything never asks, and Cursor's cloud agents never ask. See Approvals in Cursor.
Every call is written down, refusals included. The Tool calls list on the dashboard's Usage page shows them.
No unattended mode
AdCopilot does not change anything on a schedule or while you are away. You can run the read-only daily check-in on a timer from your own AI client (see The daily routine); any change it finds comes to you as a proposal.
Related
Add AdCopilot to your agent
Three MCP directories that list AdCopilot (the Official MCP Registry, Glama and MCP Market), and how to add it to your AI assistant from one of them.
It can never delete
AdCopilot has no tool that deletes a campaign, ad group, ad, keyword or asset, and refuses REMOVED. You pause instead. A negative keyword can be taken out.