set_segment_members
Replace the members of a STATIC customer segment with the given account IDs. The segment is converted to STATIC.
This record as markdown: /tools/io-favcrm-favcrm/set-segment-members.md
What set_segment_members does on FavCRM
AI agents use set_segment_members 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 |
|---|---|---|---|
segmentId | string | Yes | The segment ID |
accountIds | array | Yes | CRM account IDs to set as segment members |
Parameters from the server's own tool schema.
Why set_segment_members is rated Medium
This tool modifies customer segment membership by replacing members, which is a reversible write operation on CRM data. While it affects customer targeting/grouping which could have broad downstream effects (high severity), it does not delete data irreversibly or execute external code.
From the tool's definition Tool replaces/modifies segment members with given account IDs. Description uses 'Replace', indicating data modification. Segment conversion to STATIC is a reversible state change.
Attacks that exploit this kind of access
The rule that runs set_segment_members 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 set_segment_members, this is the rule to start with:
set_segment_members 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 set_segment_members call is checked against it from then on.
Questions about set_segment_members
Replace the members of a STATIC customer segment with the given account IDs. The segment is converted to STATIC. 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.
set_segment_members accepts 2 parameters: segmentId, accountIds. Required: segmentId, accountIds. 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 set_segment_members: 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.
set_segment_members 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 set_segment_members 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 set_segment_members. 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.
set_segment_members 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