AI agents use update_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 |
|---|---|---|---|
id | number | Yes | Advertiser ID |
name | string | — | 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.
This tool creates or modifies data reversibly by updating an advertiser record. It is not destructive (does not delete), not financial (no money movement), and not execute (does not run arbitrary code). The moderate severity reflects that misconfiguration of advertising accounts could affect campaigns and spending, but changes are typically reversible.
From the tool's definition Tool name 'update_advertiser' and description 'Update an existing advertiser' indicate modification of existing data.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
Update an existing 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.
update_advertiser accepts 7 parameters: id, name, email, metadata, password, can_add_ad_items, can_change_password. 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_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.
update_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 update_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 update_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.
update_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.
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 →