search_youtube_channels
AI agents call search_youtube_channels to retrieve information from YouTube Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Searching for YouTube channels is a read-only operation that queries the YouTube Data API and retrieves public information without modifying, executing, or deleting any data. The blast radius of misuse is minimal—it can only return publicly available channel information.
From the tool's definition Tool name 'search_youtube_channels' and sibling tools ('search_youtube', 'search_youtube_by_channel', 'search_youtube_videos') are all search/query operations.
Attacks that exploit this kind of access
search_youtube_channels. It is categorised as a Read tool in the YouTube Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YouTube Search MCP Server MCP server in PolicyLayer and add a rule for search_youtube_channels: 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 Search MCP Server. Nothing to install.
search_youtube_channels 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_youtube_channels 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_youtube_channels. 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_youtube_channels is provided by the YouTube Search MCP Server MCP server (knightmode/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 →