Get detailed information about a YouTube video
AI agents call youtube_get_video to retrieve information from Youtube Connector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query/fetch operation that retrieves metadata about an existing public YouTube video. It has no side effects, does not modify data, and does not execute code or trigger external operations. The worst-case misuse is retrieving sensitive metadata that should not be exposed, which is a confidentiality risk but not a destructive, financial, or code-execution risk.
From the tool's definition Tool retrieves 'detailed information about a YouTube video' via the YouTube Data API v3, with no description of modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access youtube_get_video gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Youtube Connector, and nothing reaches the server without passing your rules. This is the rule we recommend for youtube_get_video:
{
"version": "1",
"default": "deny",
"tools": {
"youtube_get_video": {}
}
} youtube_get_video is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a YouTube video. It is categorised as a Read tool in the Youtube Connector MCP Server, which means it retrieves data without modifying state.
Register the Youtube Connector 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 Youtube Connector. 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 Youtube Connector MCP server (shellydeng08/youtube-connector-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Youtube Connector tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Youtube Connector tools catalogued and risk-classified — across an index of 42,500+ MCP servers.