Get video metadata including available captions, chapters, and languages
AI agents call get_video_info to retrieve information from YouTube 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 and queries YouTube video metadata (captions, chapters, languages) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk—misuse would only expose publicly available video information, posing no security threat to systems or data integrity.
From the tool's definition Tool name 'get_video_info' and description 'Get video metadata including available captions, chapters, and languages' indicate pure data retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get video metadata including available captions, chapters, and languages. It is categorised as a Read tool in the YouTube MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YouTube MCP Server MCP server in PolicyLayer and add a rule for get_video_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 YouTube MCP Server. Nothing to install.
get_video_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_video_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_video_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_video_info is provided by the YouTube MCP Server MCP server (nattyraz/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 →