update_segment

Update an existing customer segment by id. Pass only the fields to change; criteria replaces the existing rules.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp

Medium RISK CLASS

Category Write

Parameters 51 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/update-segment.md

WHAT IT DOES

What update_segment does on FavCRM

AI agents use update_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	—	New segment name
`criteria`	object	—	Replace dynamic criteria, or null to clear criteria
`segmentId`	string	Yes	The segment ID to update
`description`	string	—	New segment description
`segmentType`	string	—	Change segment type

Parameters from the server's own tool schema.

RISK

Why update_segment is rated Medium

This tool modifies customer segment definitions, which are reversible changes to data structure and rules. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or retrieve data without side effects (Read).

From the tool's definition Tool name 'update_segment' and description 'Update an existing customer segment by id' indicates modification of existing data. The phrase 'criteria replaces the existing rules' confirms reversible changes to segment configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_segment, this is the rule to start with:

update_segment Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_segment": {
      "limits": [
        {
          "counter": "update_segment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every update_segment call is checked against it from then on.

FAQ

Questions about update_segment

What does the update_segment tool do? +

Update an existing customer segment by id. Pass only the fields to change; criteria replaces the existing rules. 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.

What parameters does update_segment accept? +

update_segment accepts 5 parameters: name, criteria, segmentId, description, segmentType. Required: segmentId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_segment? +

Register the FavCRM MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_segment? +

update_segment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_segment? +

Yes. Add a rate_limit block to the update_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.

How do I block update_segment completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_segment? +

update_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.

KEEP EXPLORING

More on FavCRM, and thousands of servers like it.

This server

All 220 FavCRM tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →