Creates a new Search or Display campaign in the specified
AI agents use google_ads_campaigns_create 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.
The tool creates new advertising campaigns, which are reversible changes to the Google Ads account structure. While it modifies financial advertising spend configuration, it does not directly move money or commit financial transactions—it only creates campaign infrastructure. This makes it Write rather than Financial.
From the tool's definition Tool name includes 'create' and description states 'Creates a new Search or Display campaign'. This is a write operation that modifies advertising account state by adding a new campaign resource.
Documented attack patterns abuse exactly the kind of access google_ads_campaigns_create 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_campaigns_create:
{
"version": "1",
"default": "deny",
"tools": {
"google_ads_campaigns_create": {
"limits": [
{
"counter": "google_ads_campaigns_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}google_ads_campaigns_create 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.
Creates a new Search or Display campaign in the specified. 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_campaigns_create: 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_campaigns_create 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_create 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_create. 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_create 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.