AI agents use create_publisher 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 | Publisher name |
email | string | — | Contact email (allows publisher to log in) |
domain | string | — | Publisher domain (top-level domains only) |
metadata | object | — | Custom metadata key-value pairs |
timezone | string | — | Timezone (e.g., "America/New_York") |
seller_type | string | — | Seller type for ads.txt |
default_payout | object | — | Default payout configuration |
can_approve_ads | boolean | — | Allow publisher to approve/deny ad items |
can_admin_account | boolean | — | Grant administrator privileges |
can_change_password | boolean | — | Whether publisher can change password |
can_view_wordpress_key | boolean | — | Allow publisher to view WordPress key |
Parameters from the server's own tool schema.
This tool creates a new publisher entity in the AdButler ad management system. Creation of publishers is a reversible write operation—publishers can be archived, modified, or deleted. The impact is limited to advertising management records without financial transactions, deletions, or code execution.
From the tool's definition Tool name 'create_publisher' and description 'Create a new publisher' indicate data creation, which is a reversible write operation typical of administrative platform management.
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
Create a new publisher. 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_publisher accepts 11 parameters: name, email, domain, metadata, timezone, seller_type, default_payout, can_approve_ads, can_admin_account, can_change_password, can_view_wordpress_key. 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_publisher: 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_publisher 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_publisher 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_publisher. 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_publisher 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 →