youtube_search
Search YouTube for videos, channels, or playlists
This record as markdown: /tools/io-github-alifanov-scopegate/youtube-search.md
What youtube_search does on ScopeGate
AI agents call youtube_search to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why youtube_search is rated Low
YouTube search is a read-only information retrieval operation. It queries public YouTube data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could perform excessive searches but cannot harm data, finances, or external systems.
From the tool's definition Tool name is 'youtube_search' and description states it 'Search[es] YouTube for videos, channels, or playlists' — a pure query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs youtube_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For youtube_search, this is the rule to start with:
youtube_search 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 ScopeGate, apply this rule, and every youtube_search call is checked against it from then on.
Questions about youtube_search
Search YouTube for videos, channels, or playlists. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.
Register the ScopeGate MCP server in PolicyLayer and add a rule for youtube_search: 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 ScopeGate. Nothing to install.
youtube_search 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_search 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_search. 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_search is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue