list_segments
List the live lead segment tags for the current company with server-computed lead counts (excluding do-not-contact, archived, and test leads). Segments are the exact comma-separated tokens in crm_leads.source (CSV event imports, website, etc.). Read-only — returns tags and counts only, never lead...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/list-segments.md
What list_segments does on Freedom Mcp
AI agents call list_segments to retrieve information from Freedom Mcp 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 |
|---|---|---|---|
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
Parameters from the server's own tool schema.
Why list_segments is rated Low
This tool retrieves and queries aggregated metadata (segment tags and counts) with no side effects, modifications, or sensitive personal data exposure. It is purely informational, serving to enumerate available segments before further operations. Fits the 'Read' category definition: retrieves or queries data with no side effects.
From the tool's definition Tool description explicitly states: 'Read-only — returns tags and counts only, never lead names/emails.' Lists segment tags and counts without retrieving or exposing individual lead data.
Attacks that exploit this kind of access
The rule that runs list_segments safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_segments, this is the rule to start with:
list_segments 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 Freedom Mcp, apply this rule, and every list_segments call is checked against it from then on.
Questions about list_segments
List the live lead segment tags for the current company with server-computed lead counts (excluding do-not-contact, archived, and test leads). Segments are the exact comma-separated tokens in crm_leads.source (CSV event imports, website, etc.). Read-only — returns tags and counts only, never lead names/emails. Use when the operator asks which lead segments or event tags exist, or before segment_leads to resolve a loosely-named segment to its exact tag. Routing: CRM/sales → what lead segments/events exist → use this. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
list_segments accepts 1 parameter: companyId. Required: companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for list_segments: 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 Freedom Mcp. Nothing to install.
list_segments 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 list_segments 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 list_segments. 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.
list_segments is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue