AI agents use update_rich_media_ad_item to create or update resources in AdButler — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdButler environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Ad item ID |
name | string | — | Ad item name |
creative | number | — | Rich media creative ID |
location | string | — | Click-through URL |
metadata | object | — | Custom metadata key-value pairs |
tracking_pixel | string | — | Third-party tracking pixel URL |
tracking_pixels | array | — | Array of tracking pixel URLs |
html_content_below | string | — | HTML content below the ad item |
trusted_redirect_domains | array | — | Trusted redirect domains |
expand_vertical_direction | string | — | Vertical expand direction |
expand_horizontal_direction | string | — | Horizontal expand direction |
Parameters from the server's own tool schema.
The tool modifies an existing ad item's properties reversibly. This is a Write operation—data is changed but not deleted. Severity is medium because updates to ad campaign items could affect advertising delivery and impressions, but the change is not destructive and is typically reversible through subsequent updates. Confidence is high because the intent is explicitly stated in the description.
From the tool's definition Tool name contains 'update' and description states 'Update an existing rich media ad item', indicating modification of existing data.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
Update an existing rich media ad item. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_rich_media_ad_item accepts 11 parameters: id, name, creative, location, metadata, tracking_pixel, tracking_pixels, html_content_below, trusted_redirect_domains, expand_vertical_direction, expand_horizontal_direction. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for update_rich_media_ad_item: 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 AdButler. Nothing to install.
update_rich_media_ad_item 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 update_rich_media_ad_item 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 update_rich_media_ad_item. 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.
update_rich_media_ad_item is provided by the AdButler MCP server (adbutler/mcp-server). 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 →