AI agents use create_native_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 |
|---|---|---|---|
name | string | Yes | 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 |
template | number | Yes | Native template ID |
variables | object | Yes | Template variables as key-value pairs (keys should be integer strings) |
tracking_pixel | string | — | Third-party tracking pixel URL |
tracking_pixels | array | — | Array of tracking pixel URLs |
trusted_redirect_domains | array | — | Trusted redirect domains |
Parameters from the server's own tool schema.
This tool creates (writes) a new ad item, which is a reversible operation. It does not execute external code, delete data, move money, or trigger irreversible changes. The severity is medium because creating ad items could be misused to inject malicious advertising content into campaigns, but the operation itself is non-destructive and could be undone by deletion or archiving.
From the tool's definition Tool name 'create_native_ad_item' and description 'Create a new native ad item' indicate creation of new advertising content.
Risk signalsAccepts raw HTML/template content (template) · High parameter count (10 properties)
Attacks that exploit this kind of access
Create a new native ad item using a native template. 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.
create_native_ad_item accepts 10 parameters: name, width, height, location, metadata, template, variables, tracking_pixel, tracking_pixels, trusted_redirect_domains. Required: name, template, variables. 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 create_native_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.
create_native_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 create_native_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 create_native_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.
create_native_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 →