AI agents use draft_create_native_ad_item 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 |
|---|---|---|---|
draft | object | Yes | Object containing native ad item fields (name required, plus template, variables, etc.) |
campaign_draft_id | number | Yes | Draft campaign ID this ad item belongs to |
Parameters from the server's own tool schema.
This tool creates a new native ad item in draft state, which is a reversible write operation. It modifies the advertising system by adding new content, but since it creates a draft (not a published/live item), the impact is contained and reversible. The severity is medium because misuse could create unwanted ad content or spam the system, but the effect is not destructive and can be undone.
From the tool's definition Tool name contains 'create' and description states 'Create a new draft native ad item', indicating data creation. The 'draft' qualifier indicates the action is reversible (can be deleted or modified before publication).
Attacks that exploit this kind of access
Create a new draft native ad item. 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.
draft_create_native_ad_item accepts 2 parameters: draft, campaign_draft_id. Required: draft, campaign_draft_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 draft_create_native_ad_item: 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.
draft_create_native_ad_item 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 draft_create_native_ad_item 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 draft_create_native_ad_item. 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.
draft_create_native_ad_item 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 →