youtube_list_playlists
List playlists belonging to a YouTube channel.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/youtube-list-playlists.md
What youtube_list_playlists does on UnClick
AI agents call youtube_list_playlists 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 |
|---|---|---|---|
api_key | string | Yes | |
channel_id | string | Yes | |
page_token | string | — | |
max_results | number | — |
Parameters from the server's own tool schema.
Why youtube_list_playlists is rated Low
This tool queries and retrieves playlist metadata from a YouTube channel. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external state changes. It is a straightforward data retrieval operation, making it a Read-category tool with low severity.
From the tool's definition Tool name explicitly states 'list_playlists' and description says 'List playlists belonging to a YouTube channel' — both indicate a read-only query operation that retrieves existing data without modification.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs youtube_list_playlists 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 youtube_list_playlists, this is the rule to start with:
youtube_list_playlists 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 youtube_list_playlists call is checked against it from then on.
Questions about youtube_list_playlists
List playlists belonging to a YouTube channel. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
youtube_list_playlists accepts 4 parameters: api_key, channel_id, page_token, max_results. Required: api_key, channel_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 youtube_list_playlists: 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.
youtube_list_playlists 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 youtube_list_playlists 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 youtube_list_playlists. 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.
youtube_list_playlists 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