create_ortb_native_image_asset
Create a new image asset for an ORTB native template
This record as markdown: /tools/adbutler/create-ortb-native-image-asset.md
What create_ortb_native_image_asset does on AdButler
AI agents use create_ortb_native_image_asset 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 |
|---|---|---|---|
h | number | — | Height |
w | number | — | Width |
hmin | number | — | Min height |
type | number | — | Image asset type |
wmin | number | — | Min width |
template_id | number | Yes | ORTB native template ID |
Parameters from the server's own tool schema.
Why create_ortb_native_image_asset is rated Medium
This tool creates a new image asset in the ad management system, which is a reversible data modification operation. It does not execute arbitrary code, delete data irreversibly, or move money. The 'create' action falls under the Write category. Severity is medium because misuse could result in creation of unwanted or malicious ad assets, but the impact is confined to ad management and is reversible.
From the tool's definition Tool name 'create_ortb_native_image_asset' and description 'Create a new image asset for an ORTB native template' explicitly state a create operation that adds a new asset to the AdButler system.
Attacks that exploit this kind of access
The rule that runs create_ortb_native_image_asset safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_ortb_native_image_asset, this is the rule to start with:
create_ortb_native_image_asset 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every create_ortb_native_image_asset call is checked against it from then on.
Questions about create_ortb_native_image_asset
Create a new image asset for an ORTB 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_ortb_native_image_asset accepts 6 parameters: h, w, hmin, type, wmin, template_id. Required: template_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 create_ortb_native_image_asset: 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_ortb_native_image_asset 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_ortb_native_image_asset 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_ortb_native_image_asset. 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_ortb_native_image_asset 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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue