segment_identify_user
Identify a user in Segment with traits. Links an anonymous ID to a known user ID.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/segment-identify-user.md
What segment_identify_user does on UnClick
AI agents use segment_identify_user to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
traits | object | — | User traits as key-value pairs (e.g. name, email, plan) |
user_id | string | — | Unique user identifier |
timestamp | string | — | ISO 8601 timestamp (defaults to now) |
write_key | string | Yes | Segment source write key |
anonymous_id | string | — | Anonymous ID to link to the user |
Parameters from the server's own tool schema.
Why segment_identify_user is rated Medium
This tool creates or modifies user identity data in Segment by associating traits with a user and linking anonymous IDs to known user IDs. This is a reversible write operation — it updates identity/profile data but does not delete or irreversibly destroy anything. Misuse could lead to identity mapping errors or PII exposure, hence medium severity.
From the tool's definition Identify a user in Segment with traits. Links an anonymous ID to a known user ID.
Attacks that exploit this kind of access
The rule that runs segment_identify_user 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 segment_identify_user, this is the rule to start with:
segment_identify_user stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 segment_identify_user call is checked against it from then on.
Questions about segment_identify_user
Identify a user in Segment with traits. Links an anonymous ID to a known user ID. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
segment_identify_user accepts 5 parameters: traits, user_id, timestamp, write_key, anonymous_id. Required: write_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 segment_identify_user: 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_identify_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the segment_identify_user 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_identify_user. 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_identify_user 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