youtube_playlist
HTTP: GET /v1/youtube/playlist/{id}
This record as markdown: /tools/com-replynodes-mcp/youtube-playlist.md
What youtube_playlist does on ReplyNodes
AI agents call youtube_playlist to retrieve information from ReplyNodes 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 |
|---|---|---|---|
id | string | Yes | path parameter |
language | string | — | query parameter |
Parameters from the server's own tool schema.
Why youtube_playlist is rated Low
Tool fetches public YouTube playlist information without modifying or executing operations.
From the tool's definition GET /v1/youtube/playlist/{id} retrieves YouTube playlist data
Attacks that exploit this kind of access
The rule that runs youtube_playlist safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ReplyNodes, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For youtube_playlist, this is the rule to start with:
youtube_playlist 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 ReplyNodes, apply this rule, and every youtube_playlist call is checked against it from then on.
Questions about youtube_playlist
HTTP: GET /v1/youtube/playlist/{id}. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.
youtube_playlist accepts 2 parameters: id, language. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the ReplyNodes MCP server in PolicyLayer and add a rule for youtube_playlist: 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 ReplyNodes. Nothing to install.
youtube_playlist 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_playlist 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_playlist. 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_playlist is provided by the ReplyNodes MCP server (https://mcp.replynodes.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ReplyNodes, and thousands of servers like it.
This server
Across the catalogue