Buscar videos en YouTube
AI agents call search_videos to retrieve information from YouTube MCP Server 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 operation to retrieve and display YouTube videos matching specified criteria. It has no side effects—it only reads and returns data from YouTube's public search results. No data is created, modified, deleted, or financial obligations incurred. The blast radius of misuse is minimal, limited to potential information disclosure or API rate limit consumption.
From the tool's definition Tool name 'search_videos' and description 'Buscar videos en YouTube' (Search videos on YouTube) indicates a query operation that retrieves video information without modifying or deleting data.
Attacks that exploit this kind of access
Buscar videos en YouTube. It is categorised as a Read tool in the YouTube MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YouTube MCP Server MCP server in PolicyLayer and add a rule for search_videos: 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 MCP Server. Nothing to install.
search_videos 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_videos 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_videos. 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_videos is provided by the YouTube MCP Server MCP server (nocodeboy/youtube-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 →