search_youtube
AI agents call search_youtube to retrieve information from Unified Search 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 or queries YouTube video data with no modification, deletion, or execution capabilities. It follows the 'search' pattern established by sibling tools (search_google_scholar, search_google_web). Although the tool description is empty, the server's stated purpose and naming convention strongly indicate this is a Read operation.
From the tool's definition Tool name is 'search_youtube' and server description indicates it 'Supports simultaneous multi-source searches' for 'videos' with 'filtering options'. The verb 'search' and context of querying video content indicates data retrieval without side effects.
Attacks that exploit this kind of access
search_youtube. It is categorised as a Read tool in the Unified Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unified Search MCP Server MCP server in PolicyLayer and add a rule for search_youtube: 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 Unified Search MCP Server. Nothing to install.
search_youtube 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 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. 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 is provided by the Unified Search MCP Server MCP server (jdeun/unified-search-mcp-server). 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 →