AI agents use google_ads.campaigns.update_budget 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.
The tool modifies (updates) campaign budget data in Google Ads, which is a write operation. While budgets have financial implications, the tool itself updates budget configuration rather than moving money directly, so it is categorized as Write rather than Financial. Severity is high because misconfiguration could cause significant unintended ad spend or campaign disruption.
From the tool's definition Tool name includes 'update_budget' and description states 'Update a Google Ads campaign', indicating modification of campaign budget settings. This is a reversible write operation on financial campaign configuration.
Attacks that exploit this kind of access
Update a Google Ads campaign. 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.update_budget: 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.update_budget 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.update_budget 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.update_budget. 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.update_budget 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 →