Ad Platform Agent Auth Review
Review DV360, Google Ads, and similar ad-platform agents for personal OAuth risk, workspace scoping, token storage, read/write separation, and approval readiness.
Use before an agent reads or writes to DV360, Google Ads, Meta Ads, product feeds, or commerce/analytics APIs using OAuth or service credentials.
Inputs
Collect:
- Platforms connected: DV360, Google Ads, Meta Ads, Merchant Center, warehouse, CRM, CMS.
- Credential type: personal OAuth, service account, API key, app token, internal execution grant.
- Requested scopes and actual platform permissions.
- Advertiser/workspace/client mapping.
- Actions: read, propose, approve, execute, rollback.
- Token storage location and rotation process.
- Whether the LLM can see tokens, tool outputs, or raw API credentials.
- Current approval and audit flow.
Outputs
- Authentication risk report
- Trust-zone recommendation
- Read/write separation checklist
- Approval-gated execution recommendation
Before you begin
- Reading and copying the procedure require no terminal setup. Check requirements for any packaged programs separately.
Try this first
Read the procedure and supply its documented inputs. Use the full text in an agent app or chat that supports pasted instructions, following that host's guidance.
Limits for this step
- Instruction package only; it does not provide or authorize an executable runtime capability.
- Analysis-only; must not create tokens, change OAuth scopes, approve access, or execute ad-platform writes.
Read full instructionsHide full instructions
Ad Platform Agent Auth Review
When to use
Use this skill when a team is building or reviewing an agent that connects to DV360, Google Ads, Meta Ads, Merchant Center, product feeds, analytics warehouses, or other marketing platforms with OAuth, API keys, or service credentials.
Typical triggers:
- "Our agent uses a user's Google OAuth token; is that safe?"
- "Can this DV360 agent move from read-only to write access?"
- "How should we scope Google Ads access for an optimisation agent?"
- "What auth risks exist before this agent changes bids, budgets, or targeting?"
- "Should this agent use personal OAuth, service account, or brokered access?"
Inputs required
Collect:
- Platforms connected: DV360, Google Ads, Meta Ads, Merchant Center, warehouse, CRM, CMS.
- Credential type: personal OAuth, service account, API key, app token, internal execution grant.
- Requested scopes and actual platform permissions.
- Advertiser/workspace/client mapping.
- Actions: read, propose, approve, execute, rollback.
- Token storage location and rotation process.
- Whether the LLM can see tokens, tool outputs, or raw API credentials.
- Current approval and audit flow.
Workflow
-
Map the credential chain.
- Identify who grants access, where refresh credentials live, and which component retrieves execution credentials.
- Flag any path where the LLM sees long-lived credentials.
-
Check scope and workspace isolation.
- Compare token/platform access with the agent's actual task.
- Flag access that crosses client, brand, market, advertiser, or workspace boundaries without explicit mapping.
-
Check identity model.
- Identify whether API writes appear as a human user, service identity, or agent-specific identity.
- Flag misleading audit trails where a human identity masks an agent action.
-
Check read/write separation.
- Confirm read-only analysis and write-capable execution use separate permissions and components.
- Flag single-token designs that can both inspect and mutate campaigns.
-
Check approval readiness.
- Identify high-risk actions: budget increases, bid changes, targeting expansion, audience edits, product-feed updates, tracking changes, publishing.
- Require step-up approval or bounded execution grants for these actions.
-
Check audit and rollback readiness.
- Confirm the system records current state, proposed diff, policy decision, approver, execution payload, post-write verification, and rollback patch.
Output format
# Ad Platform Agent Auth Review
## Decision
Read-only safe / Plan-only only / Approval-gated writes possible / Blocked
## Auth risk summary
- Credential model:
- Scope fit:
- Workspace isolation:
- Token handling:
- Audit identity:
## Findings
| Area | Status | Evidence | Required change |
| --- | --- | --- | --- |
## Recommended trust zone design
| Zone | Component | Allowed access |
| --- | --- | --- |
| User identity | ... | ... |
| Control plane | ... | ... |
| Agent runtime | ... | ... |
| Execution zone | ... | ... |
## Required before write access
1. ...
Guardrails
- Do not approve OAuth scopes or platform access.
- Do not create, rotate, expose, or request secrets.
- Do not recommend direct LLM access to long-lived refresh tokens, service keys, or API credentials.
- Treat personal OAuth used for agent writes as a production risk unless mediated by a broker and scoped per workspace.
- Treat bid, budget, targeting, audience, product-feed, and tracking changes as write-risk actions by default.
Failure modes
- If scopes are unknown, mark scope fit as unknown and recommend plan-only/read-only mode.
- If platform permissions exceed the agent task, recommend broker-level scoping before writes.
- If audit identity records only a human user for agent actions, mark audit identity as partial or misleading.
View file metadata
---
name: ad-platform-agent-auth-review
description: Review DV360, Google Ads, and similar marketing agents for unsafe OAuth, broad platform access, weak token handling, missing read/write separation, and missing approval gates.
---Install instruction files
These commands copy guidance into the selected runtime directories. Confirm that your agent app discovers it. Any packaged programs need separate setup and verification.
Install (Codex)
./bin/skills-hub install security/[email protected] --runtime codex
Install (Claude)
./bin/skills-hub install security/[email protected] --runtime claude
Install (Generic)
./bin/skills-hub install security/[email protected] --runtime generic --target ./my-agent/skills