update_campaign
Update an existing campaign. Channel cannot be changed after creation. Pass only fields to change.
This record as markdown: /tools/io-favcrm-favcrm/update-campaign.md
What update_campaign does on FavCRM
AI agents use update_campaign to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Name |
status | string | — | Status filter |
segmentId | object | — | Segment ID |
campaignId | string | Yes | Campaign ID |
scheduledAt | object | — | Scheduled timestamp (ISO 8601) |
recipientIds | array | — | Explicit recipient user IDs |
channelConfig | object | — | For email, use subject + htmlBody + optional plainTextBody. Legacy html is normalized to htmlBody. |
recipientSource | string | — | Recipient source: segment | tier | manual |
Parameters from the server's own tool schema.
Why update_campaign is rated Medium
This tool modifies campaign data in a reversible manner (existing campaigns can be further updated or restored). It does not delete data (Destructive), execute arbitrary code (Execute), transfer funds (Financial), or merely read data (Read). The severity is medium because misuse could alter marketing campaigns affecting customer communications, but changes are non-destructive and correctable.
From the tool's definition Tool name 'update_campaign' and description 'Update an existing campaign' indicates modification of existing data. The phrase 'Pass only fields to change' confirms selective updates to campaign records.
Attacks that exploit this kind of access
The rule that runs update_campaign safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_campaign, this is the rule to start with:
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 FavCRM, apply this rule, and every update_campaign call is checked against it from then on.
Questions about update_campaign
Update an existing campaign. Channel cannot be changed after creation. Pass only fields to change. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_campaign accepts 8 parameters: name, status, segmentId, campaignId, scheduledAt, recipientIds, channelConfig, recipientSource. Required: campaignId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for 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 FavCRM. Nothing to install.
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 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 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.
update_campaign is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue