Sets the daily amount on an existing campaign budget. Mutating
AI agents use google_ads_budget_update to create or update resources in Mureo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mureo environment.
This tool modifies campaign budget settings, which affects ad spend and campaign behavior. While reversible (budgets can be adjusted again), it directly impacts financial resource allocation and campaign performance. Categorized as Write rather than Financial because it adjusts budget parameters rather than moving money or creating financial obligations directly.
From the tool's definition Tool description states 'Sets the daily amount on an existing campaign budget. Mutating' — explicitly mutates (modifies) an existing resource. The term 'Mutating' confirms it is a write operation that changes campaign budget configuration.
Documented attack patterns abuse exactly the kind of access google_ads_budget_update gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mureo, and nothing reaches the server without passing your rules. This is the rule we recommend for google_ads_budget_update:
{
"version": "1",
"default": "deny",
"tools": {
"google_ads_budget_update": {
"limits": [
{
"counter": "google_ads_budget_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}google_ads_budget_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Sets the daily amount on an existing campaign budget. Mutating. It is categorised as a Write tool in the Mureo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mureo MCP server in PolicyLayer and add a rule for google_ads_budget_update: 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 Mureo. Nothing to install.
google_ads_budget_update 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_budget_update 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_budget_update. 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_budget_update is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mureo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
185 Mureo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.