This record as markdown: /tools/io-favcrm-favcrm/delete-segment.md
What delete_segment does on FavCRM
AI agents call delete_segment to permanently remove resources in FavCRM, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
segmentId | string | Yes | The segment ID to delete |
Parameters from the server's own tool schema.
Why delete_segment is rated Critical
This tool performs an irreversible deletion operation on a customer segment. Segments are typically collections of customers grouped by criteria, and deleting a segment would permanently remove that grouping and potentially associated data or configurations. This cannot be undone and represents data loss.
From the tool's definition Tool name is 'delete_segment' with description 'Delete a customer segment.' The use of 'delete' combined with 'segment' indicates irreversible removal of grouped customer data.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_segment, this is the rule to start with:
delete_segment is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every delete_segment call is checked against it from then on.
Questions about delete_segment
Delete a customer segment. It is categorised as a Destructive tool in the FavCRM MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_segment accepts 1 parameter: segmentId. Required: segmentId. 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 delete_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.
delete_segment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue