Search for videos within a specific YouTube channel.
AI agents call search_within_channel 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.
This tool retrieves and queries video data from a YouTube channel. It performs a search operation to locate videos matching criteria, returning results without creating, modifying, deleting, or executing any operations. No side effects occur from querying channel video data.
From the tool's definition Tool name 'search_within_channel' and description 'Search for videos within a specific YouTube channel' indicate retrieval of video metadata without modification or side effects.
Attacks that exploit this kind of access
Search for videos within a specific YouTube channel. 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 search_within_channel: 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.
search_within_channel 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 search_within_channel 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 search_within_channel. 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.
search_within_channel 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 →