klaviyo_list_segments
List Klaviyo segments (dynamic groups).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/klaviyo-list-segments.md
What klaviyo_list_segments does on UnClick
AI agents call klaviyo_list_segments to retrieve information from UnClick 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 |
|---|---|---|---|
api_key | string | Yes | Klaviyo private API key |
Parameters from the server's own tool schema.
Why klaviyo_list_segments is rated Low
This tool retrieves existing segment information from Klaviyo without modifying, deleting, or executing actions. The verb 'list' is a standard read operation. Segment data exposure is low-risk (no financial, destructive, or execute consequences) unless the segments themselves contain highly sensitive audience targeting details, but that is context-dependent and does not elevate the intrinsic operation above Read…
From the tool's definition Tool name 'list_segments' and description 'List Klaviyo segments (dynamic groups)' indicate a read-only retrieval operation.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs klaviyo_list_segments safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For klaviyo_list_segments, this is the rule to start with:
klaviyo_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 UnClick, apply this rule, and every klaviyo_list_segments call is checked against it from then on.
Questions about klaviyo_list_segments
List Klaviyo segments (dynamic groups). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
klaviyo_list_segments accepts 1 parameter: api_key. Required: api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for klaviyo_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 UnClick. Nothing to install.
klaviyo_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 klaviyo_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 klaviyo_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.
klaviyo_list_segments is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue