This record as markdown: /tools/creativelead-unclick/twitch-schedule.md
What twitch_schedule does on UnClick
AI agents call twitch_schedule 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 |
|---|---|---|---|
client_id | string | — | |
client_secret | string | — | |
broadcaster_id | string | — |
Parameters from the server's own tool schema.
Why twitch_schedule is rated Low
This tool only fetches/queries publicly available scheduling information from a Twitch channel. No data is created, modified, deleted, or executed. Blast radius if misused is minimal since it only reads public data.
From the tool's definition 'Get a Twitch channel's streaming schedule' — read-only retrieval of scheduling data
Attacks that exploit this kind of access
The rule that runs twitch_schedule 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_schedule, this is the rule to start with:
twitch_schedule 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_schedule call is checked against it from then on.
Questions about twitch_schedule
Get a Twitch channel's streaming schedule. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
twitch_schedule accepts 3 parameters: 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_schedule: 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_schedule 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_schedule 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_schedule. 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_schedule 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