Returns full metadata for a single video, including tags.
AI agents call get_video_details 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 the YouTube Data API v3 to retrieve existing video metadata. It performs no creation, modification, deletion, code execution, or financial operations. The blast radius of misuse is minimal—an agent could retrieve sensitive metadata or analyze videos at scale, but cannot alter content or trigger external operations.
From the tool's definition Tool returns full metadata for a single video, including tags. The verb 'Returns' and the context of 'metadata retrieval' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Returns full metadata for a single video, including tags. 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_video_details: 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_video_details 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_details 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_details. 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_details 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 →