Search YouTube for videos, channels, or playlists
AI agents call youtube_search to retrieve information from Youtube Connector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search query against YouTube's public data, returning results without any side effects. It fits the Read category definition as a search/query operation that retrieves data. Severity is low because misuse would only expose public information already accessible through normal YouTube browsing; there is no destructive, financial, or execution risk.
From the tool's definition Tool description states 'Search YouTube for videos, channels, or playlists' with no mention of modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access youtube_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Youtube Connector, and nothing reaches the server without passing your rules. This is the rule we recommend for youtube_search:
{
"version": "1",
"default": "deny",
"tools": {
"youtube_search": {}
}
} youtube_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search YouTube for videos, channels, or playlists. It is categorised as a Read tool in the Youtube Connector MCP Server, which means it retrieves data without modifying state.
Register the Youtube Connector 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 Youtube Connector. 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 Youtube Connector MCP server (shellydeng08/youtube-connector-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Youtube Connector tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Youtube Connector tools catalogued and risk-classified — across an index of 42,500+ MCP servers.