create_segment
Create a new customer segment. Use STATIC for manual member lists, DYNAMIC for criteria-based auto-filtering.
This record as markdown: /tools/io-favcrm-favcrm/create-segment.md
What create_segment does on FavCRM
AI agents use create_segment 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 | Yes | Segment name |
criteria | object | — | Dynamic segment criteria |
description | string | — | Segment description |
segmentType | string | — | Segment type (default DYNAMIC) |
Parameters from the server's own tool schema.
Why create_segment is rated Medium
This tool creates new customer segments, which is a reversible data modification operation. While it doesn't delete or move money, creating segments that filter customers could be misused to isolate specific customer groups (e.g., high-value customers) for targeted manipulation or unauthorized outreach.
From the tool's definition The tool description states "Create a new customer segment", indicating it creates new data structures. The ability to specify STATIC or DYNAMIC types shows it modifies the CRM's segmentation configuration.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs create_segment 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 create_segment, this is the rule to start with:
create_segment 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 create_segment call is checked against it from then on.
Questions about create_segment
Create a new customer segment. Use STATIC for manual member lists, DYNAMIC for criteria-based auto-filtering. 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.
create_segment accepts 4 parameters: name, criteria, description, segmentType. Required: name. 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 create_segment: 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.
create_segment 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 create_segment 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 create_segment. 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.
create_segment 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