AI agents use upload_creative 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.
Uploading a creative asset is a reversible Write operation—it adds new ad content to the system. It is not Destructive (not irreversible), not Execute (not arbitrary code/commands), and not Financial (no direct money movement, though ad creatives ultimately drive ad spend).
From the tool's definition Tool name 'upload_creative' indicates it creates or uploads creative assets. Sibling context includes 'bulk_upload_creatives' and 'create_line_item', confirming this server manages ad content creation.
Documented attack patterns abuse exactly the kind of access upload_creative 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 upload_creative:
{
"version": "1",
"default": "deny",
"tools": {
"upload_creative": {
"limits": [
{
"counter": "upload_creative_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload_creative 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.
upload_creative. 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 upload_creative: 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.
upload_creative 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 upload_creative 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 upload_creative. 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.
upload_creative 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.