This record as markdown: /tools/adbutler/create-advertiser.md
What create_advertiser does on AdButler
AI agents use create_advertiser 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 | Advertiser name |
email | string | — | Contact email |
metadata | object | — | Custom metadata key-value pairs |
password | string | — | Password for advertiser portal (min 8 chars, must include upper, lower, number) |
can_add_ad_items | boolean | — | Whether advertiser can submit advertisements for scheduling |
can_change_password | boolean | — | Whether advertiser can change password |
Parameters from the server's own tool schema.
Why create_advertiser is rated Medium
This tool creates a new advertiser entity, which is reversible (it can be modified or archived as evidenced by the sibling 'archive_advertiser' tool). It has no destructive, financial, or code execution aspects. The blast radius is medium because creating advertiser records could impact campaign management and billing operations if misused, but the action itself is not irreversible.
From the tool's definition Tool name is 'create_advertiser' and description states 'Create a new advertiser'. The verb 'create' indicates the tool creates new data (an advertiser record) in the AdButler system.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs create_advertiser 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_advertiser, this is the rule to start with:
create_advertiser 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_advertiser call is checked against it from then on.
Questions about create_advertiser
Create a new advertiser. 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_advertiser accepts 6 parameters: name, email, metadata, password, can_add_ad_items, can_change_password. Required: name. 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_advertiser: 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_advertiser 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_advertiser 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_advertiser. 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_advertiser 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