Fetch top-level YouTube comments for one video.
AI agents call get_video_comments to retrieve information from Youtube Research 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 comments without any side effects, modification, or execution of code. It is a straightforward data collection operation consistent with the Read category (query/fetch operations). The severity is low because the blast radius of misuse is minimal—an agent could retrieve comments at scale but cannot damage data or systems.
From the tool's definition Tool name 'get_video_comments' and description 'Fetch top-level YouTube comments for one video' indicate a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access get_video_comments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Youtube Research, and nothing reaches the server without passing your rules. This is the rule we recommend for get_video_comments:
{
"version": "1",
"default": "deny",
"tools": {
"get_video_comments": {}
}
}get_video_comments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch top-level YouTube comments for one video. It is categorised as a Read tool in the Youtube Research MCP Server, which means it retrieves data without modifying state.
Register the Youtube Research 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 Research. 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 Research MCP server (lee-s-dev/youtube-research-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Youtube Research, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Youtube Research tools catalogued and risk-classified — across an index of 43,000+ MCP servers.