get_video_metrics
AI agents call get_video_metrics to retrieve information from YouTube Content Management MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves video metrics/analytics from YouTube Data API v3. Despite the empty description, the name and context (metrics retrieval on a content analysis server with other read-only query tools) clearly indicate a data retrieval operation with no capacity to modify, delete, or execute actions. The blast radius of misuse is minimal—an agent could only retrieve statistics, not alter content or state.
From the tool's definition Tool name 'get_video_metrics' and sibling tools (fetch_transcripts, get_channel_metrics, get_playlist_metrics, search_*) all indicate retrieval and analysis operations.
Attacks that exploit this kind of access
get_video_metrics. It is categorised as a Read tool in the YouTube Content Management MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YouTube Content Management MCP Server MCP server in PolicyLayer and add a rule for get_video_metrics: 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 Content Management MCP Server. Nothing to install.
get_video_metrics 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_video_metrics 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_video_metrics. 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_video_metrics is provided by the YouTube Content Management MCP Server MCP server (nastyrunner13/youtube-content-management-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 →