This record as markdown: /tools/creativelead-unclick/twitch-get-clips.md
What twitch_get_clips does on UnClick
AI agents call twitch_get_clips 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 |
|---|---|---|---|
first | number | — | |
game_id | string | — | |
client_id | string | — | |
client_secret | string | — | |
broadcaster_id | string | — |
Parameters from the server's own tool schema.
Why twitch_get_clips is rated Low
This tool retrieves publicly available Twitch clip data without side effects. It queries an external API and returns results without modifying any state. This is a straightforward read operation with minimal security risk.
From the tool's definition Tool name 'twitch_get_clips' and description 'Get clips for a Twitch broadcaster' indicate data retrieval only. The verb 'Get' and 'for' (retrieval preposition) show no modification, creation, or deletion of data.
Attacks that exploit this kind of access
The rule that runs twitch_get_clips 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 twitch_get_clips, this is the rule to start with:
twitch_get_clips 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 twitch_get_clips call is checked against it from then on.
Questions about twitch_get_clips
Get clips for a Twitch broadcaster. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
twitch_get_clips accepts 5 parameters: first, game_id, client_id, client_secret, broadcaster_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 twitch_get_clips: 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.
twitch_get_clips 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 twitch_get_clips 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 twitch_get_clips. 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.
twitch_get_clips is provided by the UnClick MCP server (creativelead/unclick). 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