Fetch YouTube comments by video ID.
AI agents call get_comments_yt to retrieve information from Whats Trending on Social Media without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves YouTube comments associated with a video ID. It is a read-only operation that queries and returns existing data without creating, modifying, deleting, or executing any operations. Fetching publicly available comments has minimal security risk even if misused by an AI agent, as it merely exposes data already public on the platform.
From the tool's definition Tool name 'get_comments_yt' and description 'Fetch YouTube comments by video ID' indicate retrieval of publicly available data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_comments_yt gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Whats Trending on Social Media, and nothing reaches the server without passing your rules. This is the rule we recommend for get_comments_yt:
{
"version": "1",
"default": "deny",
"tools": {
"get_comments_yt": {}
}
}get_comments_yt 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 YouTube comments by video ID. It is categorised as a Read tool in the Whats Trending on Social Media MCP Server, which means it retrieves data without modifying state.
Register the Whats Trending on Social Media MCP server in PolicyLayer and add a rule for get_comments_yt: 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 Whats Trending on Social Media. Nothing to install.
get_comments_yt 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_comments_yt 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_comments_yt. 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_comments_yt is provided by the Whats Trending on Social Media MCP server (rugvedp/trends-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Whats Trending on Social Media, 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.
6 Whats Trending on Social Media tools catalogued and risk-classified — across an index of 43,000+ MCP servers.