create_native_template
Create a new native ad template with HTML and variable placeholders
This record as markdown: /tools/adbutler/create-native-template.md
What create_native_template does on AdButler
AI agents use create_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 |
|---|---|---|---|
name | string | Yes | Template name |
raw_html | string | Yes | HTML template content with variable placeholders (e.g. "[%title%]") |
variables | array | Yes | Array of template variables |
Parameters from the server's own tool schema.
Why create_native_template is rated Medium
This tool creates a new native ad template with HTML and placeholders in the AdButler advertising platform. It is a create operation that results in a reversible, non-destructive change to the ad system. If misused by an agent, it could create unwanted templates or templates with malicious HTML, causing operational clutter or potential injection/rendering issues.
From the tool's definition Tool description states it will 'Create a new native ad template' – a write operation that creates new data in AdButler without deletion or destruction.
Risk signalsAccepts raw HTML/template content (raw_html)
Attacks that exploit this kind of access
The rule that runs create_native_template 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_native_template, this is the rule to start with:
create_native_template 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_native_template call is checked against it from then on.
Questions about create_native_template
Create a new native ad template with HTML and variable placeholders. 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_template accepts 3 parameters: name, raw_html, variables. Required: name, raw_html, 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_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.
create_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 create_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 create_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.
create_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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue