Computes per-video engagement metrics across a channel
AI agents call get_engagement_stats 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 retrieves and analyzes engagement statistics—a read-only operation with no side effects. It falls clearly into the Read category as it queries channel data to compute metrics. The severity is low because misuse would only expose or analyze publicly available YouTube channel metrics, with no destructive, financial, or execution-based risks.
From the tool's definition Tool name 'get_engagement_stats' and description 'Computes per-video engagement metrics across a channel' indicate data retrieval and analysis operations. No creation, modification, deletion, or execution of external operations is described.
Attacks that exploit this kind of access
Computes per-video engagement metrics 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_engagement_stats: 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_engagement_stats 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_engagement_stats 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_engagement_stats. 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_engagement_stats 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 →