AI agents use google_ads.campaigns.resume to create or update resources in Ads — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ads environment.
This tool modifies the status of an existing campaign from PAUSED to ENABLED, which is a reversible state change (it can be paused again). It falls under Write as it updates data without irreversible destruction or direct financial commitment. However, re-enabling a campaign can cause it to start spending ad budget again, which carries medium severity risk.
From the tool's definition Resume a paused Google Ads campaign by setting campaign.status to ENABLED. Dry-run by default.
Attacks that exploit this kind of access
Resume a paused Google Ads campaign by setting campaign.status to ENABLED. Dry-run by default. It is categorised as a Write tool in the Ads MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ads MCP server in PolicyLayer and add a rule for google_ads.campaigns.resume: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Ads. Nothing to install.
google_ads.campaigns.resume is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the google_ads.campaigns.resume rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for google_ads.campaigns.resume. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
google_ads.campaigns.resume is provided by the Ads MCP server (manlikemuneeb/ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →