Upload an image to an ad account
AI agents use upload_ad_image to create or update resources in Claude Meta — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Meta environment.
This tool creates or stores new media assets in an advertising platform. It is not destructive (no deletion), not financial (no payment/billing), and not execute (no code/command execution). However, given the sibling tools include campaign and ad creation functions, a malicious agent uploading inappropriate images could cause reputational harm and business impact.
From the tool's definition Tool uploads an image to an ad account. While upload operations are typically Write category (create/modify data), the high severity reflects the sensitive advertising context: images uploaded could be used in campaigns affecting business visibility, customer…
Attacks that exploit this kind of access
Upload an image to an ad account. It is categorised as a Write tool in the Claude Meta MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Meta MCP server in PolicyLayer and add a rule for upload_ad_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 Claude Meta. Nothing to install.
upload_ad_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 upload_ad_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 upload_ad_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.
upload_ad_image is provided by the Claude Meta MCP server (maxx3250/claude-meta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →