draft_update_campaign
Update an existing draft standard campaign
This record as markdown: /tools/adbutler/draft-update-campaign.md
What draft_update_campaign does on AdButler
AI agents use draft_update_campaign 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 | Draft campaign ID |
draft | object | — | Object containing standard campaign fields to update |
Parameters from the server's own tool schema.
Why draft_update_campaign is rated Medium
This tool modifies campaign data reversibly. Since it operates on 'draft' campaigns, the changes are not yet live/published and can be further edited or reverted. It is Write rather than Destructive because updates are reversible, and Destructive would require permanent deletion or overwriting.
From the tool's definition Tool name contains 'update' and description states 'Update an existing draft standard campaign', indicating modification of existing data.
Attacks that exploit this kind of access
The rule that runs draft_update_campaign 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 draft_update_campaign, this is the rule to start with:
draft_update_campaign 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 draft_update_campaign call is checked against it from then on.
Questions about draft_update_campaign
Update an existing draft standard campaign. 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_update_campaign accepts 2 parameters: id, draft. 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 draft_update_campaign: 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_update_campaign 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_update_campaign 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_update_campaign. 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_update_campaign 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