preview_segment_count
Preview how many customers would match dynamic segment criteria before creating or updating a segment.
This record as markdown: /tools/io-favcrm-favcrm/preview-segment-count.md
What preview_segment_count does on FavCRM
AI agents call preview_segment_count to retrieve information from FavCRM without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
criteria | object | — | Dynamic criteria to preview. Omit or null to count all active customers. |
Parameters from the server's own tool schema.
Why preview_segment_count is rated Low
This tool retrieves aggregate information (customer count matching criteria) for evaluation purposes before a segment is created or updated. It has no side effects, does not modify or delete data, and does not execute external operations. It is a straightforward read query used for decision support.
From the tool's definition Tool description states it 'Preview[s] how many customers would match' criteria — a query operation that returns a count without modifying data. The word 'preview' indicates a non-destructive inspection of potential results.
Attacks that exploit this kind of access
The rule that runs preview_segment_count 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 preview_segment_count, this is the rule to start with:
preview_segment_count is read-only, so it stays allowed. 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 preview_segment_count call is checked against it from then on.
Questions about preview_segment_count
Preview how many customers would match dynamic segment criteria before creating or updating a segment. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
preview_segment_count accepts 1 parameter: criteria. 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 preview_segment_count: 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.
preview_segment_count is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the preview_segment_count 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 preview_segment_count. 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.
preview_segment_count 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