Update the Status and/or HasResponded flag on an existing CampaignMember record. Use to mark members as Responded, Converted, or any custom status defined in the Campaign's member status picklist. Requires the CampaignMember ID (not the Lead/Contact ID).
AI agents use sf_update_campaign_member_status to create or update resources in Salesforce Marketing — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce Marketing environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
status | string | Yes | |
hasResponded | boolean | — | |
campaignMemberId | string | Yes |
Parameters from the server's own tool schema.
This is a Write operation because it updates existing records (CampaignMember) with new values for Status and HasResponded fields. The changes are reversible—statuses can be updated again to different values. The severity is medium rather than high because the blast radius is limited to campaign member metadata (status tracking) rather than core financial data, customer records, or destructive operations.
From the tool's definition The tool 'Update the Status and/or HasResponded flag on an existing CampaignMember record' modifies data reversibly by changing status fields on campaign member records.
Attacks that exploit this kind of access
Update the Status and/or HasResponded flag on an existing CampaignMember record. Use to mark members as Responded, Converted, or any custom status defined in the Campaign's member status picklist. Requires the CampaignMember ID (not the Lead/Contact ID). It is categorised as a Write tool in the Salesforce Marketing MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sf_update_campaign_member_status accepts 3 parameters: status, hasResponded, campaignMemberId. Required: status, campaignMemberId. The full parameter table on this page comes from the server's own tool schema.
Register the Salesforce Marketing MCP server in PolicyLayer and add a rule for sf_update_campaign_member_status: 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 Salesforce Marketing. Nothing to install.
sf_update_campaign_member_status 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 sf_update_campaign_member_status 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 sf_update_campaign_member_status. 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.
sf_update_campaign_member_status is provided by the Salesforce Marketing MCP server (salesforce-marketing-mcp). 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 →