youtube_get_video
Get metadata, statistics, and content details for a YouTube video.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/youtube-get-video.md
What youtube_get_video does on UnClick
AI agents call youtube_get_video to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | Yes | |
video_id | string | Yes |
Parameters from the server's own tool schema.
Why youtube_get_video is rated Low
This tool retrieves information about a YouTube video (metadata, statistics, content details) with no side effects. It is a query/fetch operation that does not modify, execute, delete, or create data. No financial impact. Severity is low because misuse would only expose publicly available video information.
From the tool's definition Tool description states 'Get metadata, statistics, and content details for a YouTube video' — retrieval only with no modifications, deletions, or execution of external operations.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs youtube_get_video safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For youtube_get_video, this is the rule to start with:
youtube_get_video is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every youtube_get_video call is checked against it from then on.
Questions about youtube_get_video
Get metadata, statistics, and content details for a YouTube video. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
youtube_get_video accepts 2 parameters: api_key, video_id. Required: api_key, video_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for youtube_get_video: 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 UnClick. Nothing to install.
youtube_get_video 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 youtube_get_video 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 youtube_get_video. 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.
youtube_get_video is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue