Upload a local image file to Google Ads as an image Asset
AI agents use google_ads_assets_upload_image 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 creates a new image asset in Google Ads, which is a reversible Write operation. While image uploads are generally safe, the severity is medium because: (1) they modify advertising account state, (2) uploaded assets affect ad campaigns and their cost/performance, and (3) an AI agent could upload inappropriate or brand-damaging images if not properly constrained.
From the tool's definition Tool description states: 'Upload a local image file to Google Ads as an image Asset'. The verb 'upload' combined with 'as an image Asset' indicates creation of a new resource in Google Ads.
Documented attack patterns abuse exactly the kind of access google_ads_assets_upload_image 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_assets_upload_image:
{
"version": "1",
"default": "deny",
"tools": {
"google_ads_assets_upload_image": {
"limits": [
{
"counter": "google_ads_assets_upload_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}google_ads_assets_upload_image 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 a local image file to Google Ads as an image Asset. 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_assets_upload_image: 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_assets_upload_image 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_assets_upload_image 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_assets_upload_image. 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_assets_upload_image 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.