Aggregates tags across a channel
AI agents call get_tag_analysis to retrieve information from Youtube-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and aggregates existing tag metadata from a YouTube channel. It has no side effects, does not modify data, execute code, or trigger external operations beyond API data retrieval. It fits the Read category: retrieves or queries data with no side effects. Low severity because unauthorized tag analysis poses minimal risk to users or systems.
From the tool's definition Tool name 'get_tag_analysis' and description 'Aggregates tags across a channel' indicate data retrieval and analysis only.
Attacks that exploit this kind of access
Aggregates tags across a channel. It is categorised as a Read tool in the Youtube-MCP MCP Server, which means it retrieves data without modifying state.
Register the Youtube- MCP server in PolicyLayer and add a rule for get_tag_analysis: 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. Nothing to install.
get_tag_analysis 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_tag_analysis 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_tag_analysis. 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_tag_analysis is provided by the Youtube- MCP server (yashkashte5/youtube-mcp). 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 →