AI agents use update_native_template 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 | Native template ID |
name | string | — | Template name |
raw_html | string | — | HTML template content with variable placeholders |
variables | object | — | Variables to add/remove |
Parameters from the server's own tool schema.
This tool creates or modifies data in a reversible manner. It updates an existing native ad template and allows incremental changes (add/remove variables) without deleting the template itself. Updates are typically reversible—a user can update again to correct mistakes. This does not destroy data, execute arbitrary code, move money, or retrieve data only. Write is the appropriate category.
From the tool's definition The tool is named 'update_native_template' and described as updating an existing native template with variables using add/remove format for updates. The verb 'update' and the mechanism of adding/removing variables indicate modification of existing data.
Risk signalsAccepts raw HTML/template content (raw_html) · High parameter count (12 properties)
Attacks that exploit this kind of access
Update an existing native template. Variables uses add/remove format for updates. 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_native_template accepts 4 parameters: id, name, raw_html, variables. 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_native_template: 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_native_template 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_native_template 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_native_template. 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_native_template 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 →