AI agents use segment_track_event 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 |
|---|---|---|---|
event | string | Yes | Event name (e.g. 'Item Purchased') |
user_id | string | — | Unique user identifier |
timestamp | string | — | ISO 8601 timestamp (defaults to now) |
write_key | string | Yes | Segment source write key |
properties | object | — | Event properties as key-value pairs |
anonymous_id | string | — | Anonymous ID if user is not logged in |
Parameters from the server's own tool schema.
This tool writes event data to Segment's analytics pipeline. It creates new event records but does not delete or overwrite existing data, making it a Write operation. Misuse could result in polluted analytics data or false event tracking, which has medium blast radius.
From the tool's definition 'Track a custom event in Segment' and 'recording user actions like Signed Up, Item Purchased'
Attacks that exploit this kind of access
Track a custom event in Segment. Use for recording user actions like 'Signed Up', 'Item Purchased', etc. 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_track_event accepts 6 parameters: event, user_id, timestamp, write_key, properties, anonymous_id. Required: event, 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_track_event: 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_track_event 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_track_event 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_track_event. 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_track_event 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 →