AI agents call find_channels_tool to retrieve information from YtMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries publicly available YouTube channel metadata without side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because channel search results are public information with minimal blast radius if misused by an agent.
From the tool's definition Tool name is 'find_channels_tool' and description states it 'Search[es] for YouTube channels by name or topic.' The server is explicitly described as 'read-only access to YouTube data.' No modification, deletion, execution, or financial operations are…
Attacks that exploit this kind of access
Search for YouTube channels by name or topic. It is categorised as a Read tool in the YtMCP MCP Server, which means it retrieves data without modifying state.
Register the Yt MCP server in PolicyLayer and add a rule for find_channels_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 YtMCP. Nothing to install.
find_channels_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 find_channels_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 find_channels_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.
find_channels_tool is provided by the Yt MCP server (utkarshchaudhary009/ytmcp). 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 →