youtube_list_videos
AI agents call youtube_list_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.
The tool name clearly denotes a listing/query operation typical of data retrieval. While the description is empty (reducing confidence slightly), the verb 'list' and the server context (YouTube Data API integration) indicate this fetches or queries existing video data without modification, deletion, or execution of external operations. Misuse would retrieve information but cause no direct harm.
From the tool's definition Tool name 'youtube_list_videos' indicates retrieval of video listings from a YouTube channel. The 'list' verb is a standard query operation.
Attacks that exploit this kind of access
youtube_list_videos. 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 youtube_list_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.
youtube_list_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 youtube_list_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 youtube_list_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.
youtube_list_videos is provided by the YouTube MCP Server MCP server (pauling-ai/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 →