AI agents call get_channel_info to retrieve information from Yt Fetch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves public metadata about a YouTube channel without modifying, executing code, deleting data, or moving money. It is a straightforward query operation with no side effects, fitting the Read category. Severity is low as channel information is typically public and the blast radius of misuse is limited to gathering information already available through YouTube's public interface.
From the tool's definition Tool fetches channel information from YouTube. The description indicates a retrieval operation: 'Get information about a YouTube channel.' The related tools (search_videos, get_transcripts, get_video_details, trending_analysis) all perform read-only data…
Attacks that exploit this kind of access
Get information about a YouTube channel. It is categorised as a Read tool in the Yt Fetch MCP Server, which means it retrieves data without modifying state.
Register the Yt Fetch MCP server in PolicyLayer and add a rule for get_channel_info: 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 Yt Fetch. Nothing to install.
get_channel_info 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_channel_info 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_channel_info. 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_channel_info is provided by the Yt Fetch MCP server (smith-nathanh/yt-fetch). 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 →