get_segment

Get customer segment details including type, criteria, and live member count.

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

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What get_segment does on FavCRM

AI agents call get_segment 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
`segmentId`	string	Yes	The segment ID

Parameters from the server's own tool schema.

RISK

Why get_segment is rated Low

This tool retrieves and queries segment information (type, criteria, member count) from the CRM without creating, modifying, deleting, or executing any operations. It is a pure read operation with no side effects. Severity is low as unauthorized access to segment metadata poses minimal risk to the organization.

From the tool's definition Tool name 'get_segment' and description 'Get customer segment details including type, criteria, and live member count' indicate retrieval of segment metadata and counts with no modification of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_segment Allowed

get_segment is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_segment": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_segment

What does the get_segment tool do? +

Get customer segment details including type, criteria, and live member count. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.

What parameters does get_segment accept? +

get_segment accepts 1 parameter: segmentId. Required: segmentId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_segment? +

Register the FavCRM MCP server in PolicyLayer and add a rule for get_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 get_segment? +

get_segment is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_segment? +

Yes. Add a rate_limit block to the get_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 get_segment completely? +

Set action: deny in the PolicyLayer policy for get_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 get_segment? +

get_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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →