update_ortb_native_title_asset
Update an existing title asset for an ORTB native template
This record as markdown: /tools/adbutler/update-ortb-native-title-asset.md
What update_ortb_native_title_asset does on AdButler
AI agents use update_ortb_native_title_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 |
|---|---|---|---|
id | number | Yes | Title asset ID |
len | number | — | Max length of title |
template_id | number | Yes | ORTB native template ID |
Parameters from the server's own tool schema.
Why update_ortb_native_title_asset is rated Medium
The tool modifies existing ad template data (native title asset in ORTB format) reversibly without deleting or executing arbitrary code. This is a Write operation. Severity is medium because incorrect updates could affect ad campaign performance, targeting, or compliance, but the effect is limited to a single asset and reversible.
From the tool's definition Tool name includes 'update' and description states 'Update an existing title asset' — a modification operation. Part of AdButler's ad campaign management system.
Attacks that exploit this kind of access
The rule that runs update_ortb_native_title_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 update_ortb_native_title_asset, this is the rule to start with:
update_ortb_native_title_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 update_ortb_native_title_asset call is checked against it from then on.
Questions about update_ortb_native_title_asset
Update an existing title 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_title_asset accepts 3 parameters: id, len, 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_title_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_title_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_title_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_title_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_title_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