segment_get_source

Get details for a single Segment source including settings and enabled state.

Server UnClick @unclick/mcp-server
Category Read
Risk class Low
Parameters 22 required

What segment_get_source does on UnClick

AI agents call segment_get_source 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.

ParameterTypeRequiredDescription
api_key string Yes Segment Public API token
source_id string Yes Segment source ID

Parameters from the server's own tool schema.

Why segment_get_source needs a policy

This tool retrieves configuration and status information about a Segment data source. It performs a read-only query operation with no capability to modify, delete, or execute external actions. The 'enabled state' detail is descriptive metadata, not a state change. Misuse carries minimal risk as it only exposes existing source configuration data.

From the tool's definition Tool name is 'segment_get_source' and description states 'Get details for a single Segment source' - the verb 'Get' and phrase 'Get details' indicate retrieval of information without modification or side effects.

Risk signalsHandles credentials or secrets (api_key)

Questions about segment_get_source

What does the segment_get_source tool do? +

Get details for a single Segment source including settings and enabled state. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does segment_get_source accept? +

segment_get_source 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.

How do I enforce a policy on segment_get_source? +

Register the UnClick MCP server in PolicyLayer and add a rule for segment_get_source: 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.

What risk level is segment_get_source? +

segment_get_source is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit segment_get_source? +

Yes. Add a rate_limit block to the segment_get_source 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.

How do I block segment_get_source completely? +

Set action: deny in the PolicyLayer policy for segment_get_source. 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.

What MCP server provides segment_get_source? +

segment_get_source 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.