Search YouTube videos by keyword. Returns metadata list (~200 tokens).
AI agents call search_youtube to retrieve information from MCP YouTube Intelligence without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation that retrieves and returns data (video metadata) without any side effects, data modification, or external action triggering. It is a straightforward search function that falls squarely into the Read category. The low severity reflects minimal risk even if misused, as searching public YouTube metadata poses no security, privacy, or operational threat.
From the tool's definition Tool description states 'Search YouTube videos by keyword. Returns metadata list (~200 tokens).' The verb 'Search' and the fact that it only returns metadata with no modification or execution capability indicates a retrieval-only operation.
Documented attack patterns abuse exactly the kind of access search_youtube gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP YouTube Intelligence, and nothing reaches the server without passing your rules. This is the rule we recommend for search_youtube:
{
"version": "1",
"default": "deny",
"tools": {
"search_youtube": {}
}
}search_youtube 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 videos by keyword. Returns metadata list (~200 tokens). It is categorised as a Read tool in the MCP YouTube Intelligence MCP Server, which means it retrieves data without modifying state.
Register the MCP YouTube Intelligence 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 MCP YouTube Intelligence. 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 MCP YouTube Intelligence MCP server (janghyuckyun/mcp-youtube-intelligence). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP YouTube Intelligence, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MCP YouTube Intelligence tools catalogued and risk-classified — across an index of 43,000+ MCP servers.