What a ticked-account allowlist is

On the server, on every tool call. Hiding a row in the dashboard is not the control. If the assistant names an unticked ID, the call is refused and the allowed list is named in the refusal. Routing through run_tool does not get around it. list_accounts only returns ticked accounts. That is true for reads and for writes.

1. 01Connect the platform in the Get MCP Ads dashboard and complete OAuth as the account owner.
2. 02Open the account picker for that platform. Every account starts unticked.
3. 03Tick only the client accounts this assistant may reach.
4. 04Paste the hosted MCP URL into your MCP client and ask something that names a ticked account.
5. 05Untick an account when the job ends; the next call is refused for that ID.

search_tools, describe_tool and run_tool are routing tools, not a second permission system. If the inner tool names an unticked account, the call is refused. Writes still need a ticked account and, on a paid plan, confirm set to true. Confirm does not escalate an unticked ID. See authentication and Pause a campaign from an assistant.

The URL is still https://mcp-review.getmcpads.com/mcp. The allowlist is not a second URL. It is a check on the first. Seats are people on your organisation; they share the ticked set unless you split organisations. Do not put two competing clients on one organisation with both ticked and then hope the assistant keeps them straight.

Search Console properties and GA4 properties are accounts in the same picker. Connecting a Google identity that can see fourteen GA4 properties does not expose fourteen properties. You tick the property the assistant may query. Ticking a Google Ads customer does not tick a GA4 property. Each source has its own allowlist.

A Monday question that joins Ads spend to checkout events needs a ticked customer and a ticked GA4 property. If only Ads is ticked, ga4_run_report is refused for the unticked property. That is better than silently reading the wrong brand. See Google Ads and GA4 in one MCP and Connect Search Console via MCP. Official Google Ads MCP still does not include those sources.

Pinterest advertisers, TikTok advertisers and Meta ad accounts follow the same tick. There is no X Ads source to tick. Microsoft Advertising is soon: OAuth exists, tools do not, so ticking nothing there is not a workaround. Live sources stay the six we ship.

The next call against that ID is refused. In-flight results from the previous call are already in the thread; we do not reach into the assistant to erase them. Spend, impressions and conversions are not stored here, so the next question cannot reread an unticked account. Untick before you share the connector with a broader seat.

Untick when a retainer ends, not next quarter. An agent cannot tick or untick. Dashboard WebMCP tools, when they appear, are read only and will not grow a tick action. If a vendor promises an agent can grant account access, that is a different product and a different risk. Hand the human the dashboard link and the list of IDs to tick.

Seats are not the allowlist. A viewer seat still cannot write, and still cannot see unticked accounts. Free is one ad account and read only; Agency raises the account and seat caps. See pricing rather than treating the allowlist as a plan. The agency article walks who should hold confirm.

A hosted allowlist is the wrong control when you run a local MCP as the ads user on a machine that should see everything that token sees, when you need a source we do not ship, or when you are on Free and expected a write. There is no X Ads. Microsoft Advertising has no tools yet.

• You run a local MCP as the ads user on a machine that should see everything that token sees. Then the API's own ACL is the allowlist, and you operate that risk.
• You need a source we do not ship. There is no X Ads. Microsoft Advertising has no tools yet, so ticking nothing there is not a workaround.
• You are on Free and expected a write. Writes are absent, allowlist or not.
• You wanted Meta official mcp.facebook.com/ads grant-wide reach. That is Meta's server, not this check.

Official Google Ads MCP returns customers list_accessible_customers can see for that auth. Official Meta MCP reaches whatever that Meta grant reaches. Those are first-party contracts. This gateway's contract is the tick. Use the first-party server when that is the job. Use the tick when an agency desk cannot let one prompt see every client.