AI Knowledge Hub
Menu

Tools Mcp / Adtech

Governed Ad Platform Executor

Launchable MCP executor for exact control-plane-authorized Google Ads and DV360 mutations with state revalidation, serialization, receipts, reconciliation, and rollback.

Access

Read and write · Google Ads API v25 and Display & Video 360 API v4

Setup requiredAPI or MCP integrationRequirements & limitsRelated reading

Inputs

  • A bounded provider-native plan with exact target and desired state
  • Runtime-owned credentials, policy and a separately authorized control-plane grant

Outputs

  • Plan previews, execution receipts and post-write state verification
  • Reconciliation or separately authorized rollback results

Before you begin

  • Node.js 22 or newer and the Agent Control Plane 0.2.1 package.
  • Provider OAuth access with Google Ads or DV360 mutation permission for explicitly allowlisted sandbox targets.
  • Runtime-owned executor policy, credential, signed executor identity, public grant key, stores, and audit keys.

Try this first

Review the setup requirements, access boundaries and release guide before connected use.

Limits for this step
  • Only campaign status, campaign-budget amount, ad-group status or CPC bid, and DV360 line-item status or max-average-CPM bid are supported.
  • Provider mutation APIs do not guarantee idempotency; ambiguous outcomes stop for reconciliation rather than replay.
  • Conflicting post-write state is never overwritten automatically; it requires reconciliation and a separately authorized rollback where appropriate.
  • CI uses deterministic provider simulations; live sandbox mutation evidence remains separately gated.
  • Mutations require an exact single-use control-plane grant; rollback requires a separate exact grant. Preview never grants execution authority.
Review setup requirements

Summary sources · Catalogue metadata, tool.yaml, TOOL.md, README.md, examples/approved-change.json, examples/execution-result.json · v0.2.0 · Release package

View capabilities and accessHide capabilities and accessv0.2.0

What it can do

  • Preview closed provider-native change plans without acquiring execution authority.
  • Re-read current state and atomically claim an exact short-lived control-plane grant at the effect boundary.
  • Serialize each provider resource and apply bounded status, budget, or bid updates.
  • Persist authenticated intents and receipts, verify post-write state, and reconcile ambiguous effects.
  • Apply a verified rollback patch only under a separate exact rollback grant.

Access limits

Mutations require an exact single-use control-plane grant; rollback requires a separate exact grant. Preview never grants execution authority.

Trust boundary · remote-mcp-server

Credentials and setup

  • Runtime-owned provider credential and closed executor policy
  • Separately installed Agent Control Plane with an executor identity and grant public key
  • Private local executor and control-plane stores with independent audit keys

Install tool files

These commands install package files and generate runtime configuration where supported. Confirm discovery in your agent app, then check configuration, authentication and a first useful operation.

Install (Codex)

./bin/skills-hub install --module tools --entry adtech/[email protected] --runtime codex

Install (Claude)

./bin/skills-hub install --module tools --entry adtech/[email protected] --runtime claude

Install (Generic)

./bin/skills-hub install --module tools --entry adtech/[email protected] --runtime generic --target ./my-agent/tools-mcp

How You Can Use This

Setup required

Resource form: API or MCP integration

Configuration, credentials or runtime bindings are required. Check the prerequisites and limits for your intended environment.

First run: Configure sandbox allowlists and the executor identity, preview a closed plan, then execute only the exact control-plane grant for that plan.

Setup required

  • Node.js 22 or newer and the Agent Control Plane 0.2.1 package.
  • Provider OAuth access with Google Ads or DV360 mutation permission for explicitly allowlisted sandbox targets.
  • Runtime-owned executor policy, credential, signed executor identity, public grant key, stores, and audit keys.

Current limits

  • Only campaign status, campaign-budget amount, ad-group status or CPC bid, and DV360 line-item status or max-average-CPM bid are supported.
  • Provider mutation APIs do not guarantee idempotency; ambiguous outcomes stop for reconciliation rather than replay.
  • Conflicting post-write state is never overwritten automatically; it requires reconciliation and a separately authorized rollback where appropriate.
  • CI uses deterministic provider simulations; live sandbox mutation evidence remains separately gated.
What installation and verification mean
File installation
Places package files and generated configuration in the selected directories.
Native discovery
Your agent app finds and accepts the instructions, tools or plugin registrations.
Mock execution
Exercises sample fixtures. Connected data and provider effects need a separate check.
Connected operation
Requires current configuration, provider authentication, scoped permissions and a successful operation in your intended environment.

Declared compatibility

Maintainer-reviewed information for version 0.2.0 · Reviewed 2026-10-31. This is not a live provider check.

  • Packaged API targets: Google Ads API v25 and Display & Video 360 API v4
  • Runtime: Node.js 22 or newer; requires Agent Control Plane 0.2.1
  • Uses Node's built-in HTTP functionality; no Google Ads or DV360 SDK is packaged.

Limits

  • This implemented executor retains a legacy template package ID. Other provider API versions are rejected by this release.
  • Supports only bounded campaign status/budget, ad-group status/CPC and DV360 line-item status/max-average-CPM updates.
  • Provider credentials, policy and an exact control-plane grant are required for mutations. Ambiguous outcomes require reconciliation; rollback requires a separate grant.

Reviewed governed executor release implementation

Classification: declared

Technical details and release files

Review and lifecycle

Review maturity: Experimental

Security review declaration: Not declared

Lifecycle: Active

These release declarations are separate from evidence that a workflow operates in your environment.

Runtime & Dependencies

ID: adtech/ad-platform-executor-template

Tags: adtech, executor, dv360, google-ads, governance

Runtimes: codex, claude, generic

Dependencies & Setup

MCP servers: Not documented

APIs: Not documented

Local tools: agentops/agent-control-plane-server