get_video_info
AI agents call get_video_info to retrieve information from YouTube MCP Server Enhanced without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves video information from YouTube—a read-only operation with no side effects, data modification, code execution, or destructive capability. The 'get_' prefix and position among similar data-extraction tools confirm it queries and returns video metadata without altering any state.
From the tool's definition Tool name 'get_video_info' combined with server description stating it 'enables comprehensive YouTube data extraction' including 'video metadata'.
Attacks that exploit this kind of access
get_video_info. It is categorised as a Read tool in the YouTube MCP Server Enhanced MCP Server, which means it retrieves data without modifying state.
Register the YouTube MCP Server Enhanced 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 Enhanced. 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 Enhanced MCP server (labeveryday/youtube-mcp-server-enhanced). 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 →