Get comments for a video.
AI agents call get_video_comments_tool 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 retrieves publicly available YouTube video comments without any side effects or ability to modify data. It is a straightforward read operation that queries and returns information, matching the Read category definition. Low severity because comment data is typically public and retrieving it poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_video_comments_tool' and description 'Get comments for a video' indicate retrieval of existing data with no modification, creation, deletion, or execution capability.
Attacks that exploit this kind of access
Get comments for a video. 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 get_video_comments_tool: 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.
get_video_comments_tool 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 get_video_comments_tool 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 get_video_comments_tool. 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.
get_video_comments_tool is provided by the YouTube MCP Server MCP server (temiedani/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 →