AI agents use update_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 |
id | number | Yes | Image asset ID |
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.
This tool modifies existing data within an ad management system (AdButler). It updates an image asset rather than deleting it, making it Write rather than Destructive. The blast radius is medium because misconfiguration could corrupt advertising assets affecting campaigns, but the effect is reversible through subsequent updates. Not Financial because it doesn't move money.
From the tool's definition Tool name 'update_ortb_native_image_asset' and description 'Update an existing image asset for an ORTB native template' indicate modification of existing data (image assets in an advertising platform).
Attacks that exploit this kind of access
Update an existing 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.
update_ortb_native_image_asset accepts 7 parameters: h, w, id, hmin, type, wmin, template_id. Required: id, 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 update_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.
update_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 update_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 update_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.
update_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.
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 →