AI agents use create_campaign to create or update resources in Google Ad Manager MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Ad Manager MCP Server environment.
Creating a campaign is a reversible Write operation—it creates new advertising entity data in Google Ad Manager. Severity is high because a misconfigured campaign could result in wasted ad spend or incorrect audience targeting, but it is not Destructive (campaigns can be deleted/archived), Financial (no direct money transfer, though it enables spending), or Execute (no arbitrary code execution).
From the tool's definition Tool name 'create_campaign' and server context indicate creation of advertising campaigns in Google Ad Manager.
Documented attack patterns abuse exactly the kind of access create_campaign gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Ad Manager MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_campaign:
{
"version": "1",
"default": "deny",
"tools": {
"create_campaign": {
"limits": [
{
"counter": "create_campaign_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_campaign 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.
create_campaign. It is categorised as a Write tool in the Google Ad Manager MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Ad Manager MCP Server MCP server in PolicyLayer and add a rule for create_campaign: 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 Google Ad Manager MCP Server. Nothing to install.
create_campaign 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 create_campaign 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 create_campaign. 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.
create_campaign is provided by the Google Ad Manager MCP Server MCP server (matiouscorp/google-ad-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Ad Manager MCP Server, 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.
35 Google Ad Manager MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.