AI agents call segment_list_destinations to retrieve information from UnClick without modifying anything — 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 | Segment Public API token |
source_id | string | Yes | Segment source ID |
Parameters from the server's own tool schema.
This tool retrieves configuration information about data pipeline destinations without modifying or deleting anything. It is a Read operation. The severity is medium rather than low because Segment destinations may reveal sensitive information about where customer data flows and integrations in use, which could inform social engineering or further attacks, though the tool itself performs no destructive or financial…
From the tool's definition Tool name contains 'list' and description states 'List all destinations' - a retrieval operation with no modification capability. However, Segment is a customer data platform that consolidates sensitive user and business analytics data.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
List all destinations connected to a Segment source. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
segment_list_destinations accepts 2 parameters: api_key, source_id. Required: api_key, source_id. 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 segment_list_destinations: 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.
segment_list_destinations 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 segment_list_destinations 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 segment_list_destinations. 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.
segment_list_destinations 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →