AI agents use update_custom_html_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 |
width | number | — | Ad width in pixels |
height | number | — | Ad height in pixels |
location | string | — | Click-through URL |
metadata | object | — | Custom metadata key-value pairs |
custom_html | string | — | The HTML content |
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 |
Parameters from the server's own tool schema.
This tool creates or modifies data (ad item content) in a reversible manner, matching the Write category. Severity is medium because modifying ad content could affect ad campaigns and spending, but the change is reversible (can be updated again). The tool does not delete data (Destructive), execute code (Execute), move money (Financial), or irreversibly destroy information.
From the tool's definition update_custom_html_ad_item updates an existing custom HTML ad item, modifying ad creative content in the AdButler advertising platform.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
Update an existing custom HTML 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_custom_html_ad_item accepts 12 parameters: id, name, width, height, location, metadata, custom_html, tracking_pixel, tracking_pixels, html_content_below, trusted_redirect_domains, expand_vertical_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_custom_html_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_custom_html_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_custom_html_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_custom_html_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_custom_html_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 →