Get recent videos from a YouTube channel. Supports sorting by date or view count.
AI agents call get_channel_videos to retrieve information from YouTube MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and retrieves video listings from a public YouTube channel—a pure read operation with no side effects. No data is created, modified, deleted, or executed. Even if an AI agent misuses it, the worst outcome is fetching unintended channel data, which poses minimal risk since YouTube channel videos are typically public.
From the tool's definition Tool name 'get_channel_videos' and description states 'Get recent videos from a YouTube channel' with sorting options. This retrieves metadata without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get recent videos from a YouTube channel. Supports sorting by date or view count. It is categorised as a Read tool in the YouTube MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YouTube MCP Server MCP server in PolicyLayer and add a rule for get_channel_videos: 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 YouTube MCP Server. Nothing to install.
get_channel_videos 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 get_channel_videos 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 get_channel_videos. 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.
get_channel_videos is provided by the YouTube MCP Server MCP server (wynandw87/claude-code-youtube-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →