get_segment_members
Get the members that belong to a specific segment.
This record as markdown: /tools/io-favcrm-favcrm/get-segment-members.md
What get_segment_members does on FavCRM
AI agents call get_segment_members 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 |
|---|---|---|---|
limit | number | — | Max results (default 20) |
segmentId | string | Yes | The segment ID |
Parameters from the server's own tool schema.
Why get_segment_members is rated Low
This tool queries and retrieves data about segment members from the CRM system. It performs a read-only operation to fetch existing information without creating, modifying, deleting, or executing any actions. The blast radius is minimal as it only returns data the agent can already access within the CRM context.
From the tool's definition Tool name 'get_segment_members' and description 'Get the members that belong to a specific segment' indicate a retrieval operation with no modification or execution of external effects.
Attacks that exploit this kind of access
The rule that runs get_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 get_segment_members, this is the rule to start with:
get_segment_members 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 get_segment_members call is checked against it from then on.
Questions about get_segment_members
Get the members that belong to a specific segment. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
get_segment_members accepts 2 parameters: limit, 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 get_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.
get_segment_members 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 get_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 get_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.
get_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