AI agents call youtube_list_channel_videos to retrieve information from Google without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Listing videos from a YouTube channel is a read-only operation that retrieves data without modifying, executing code, or causing side effects. The 'list' verb and context of a Google Workspace integration support Read classification. Confidence is moderate (0.85) due to empty description, but the naming convention and sibling tools strongly suggest read-only behavior.
From the tool's definition Tool name 'youtube_list_channel_videos' indicates a listing/retrieval operation. Description is empty, but the name and sibling tools (calendar_list_events, calendar_list_today, ado_get_backlog) suggest this follows a Read pattern common across the server.
Attacks that exploit this kind of access
youtube_list_channel_videos. It is categorised as a Read tool in the Google MCP Server, which means it retrieves data without modifying state.
Register the Google MCP server in PolicyLayer and add a rule for youtube_list_channel_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 Google. Nothing to install.
youtube_list_channel_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_channel_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_channel_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_channel_videos is provided by the Google MCP server (psckeithw/mcp-google). 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 →