get_video_comments
AI agents call get_video_comments to retrieve information from YouTube MCP Server Enhanced without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries comment data from YouTube videos without creating, modifying, or deleting any data. It is a read-only operation with no side effects. The lack of description lowers confidence slightly, but the name and server context strongly indicate a data retrieval function. Blast radius is low—retrieving comments poses minimal security risk.
From the tool's definition Tool name 'get_video_comments' indicates retrieval of comment data. Server description explicitly lists 'comments' as a data extraction capability with no mention of modification or deletion of comments.
Attacks that exploit this kind of access
get_video_comments. It is categorised as a Read tool in the YouTube MCP Server Enhanced MCP Server, which means it retrieves data without modifying state.
Register the YouTube MCP Server Enhanced MCP server in PolicyLayer and add a rule for get_video_comments: 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 Enhanced. Nothing to install.
get_video_comments 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 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. 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 is provided by the YouTube MCP Server Enhanced MCP server (labeveryday/youtube-mcp-server-enhanced). 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 →