AI agents call getVideoDetails to retrieve information from Yt 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 video metadata and statistics from YouTube without creating, modifying, executing code, deleting data, or moving money. It is a straightforward data retrieval operation with no capability to alter state. The blast radius if misused by an AI agent is minimal—it can only expose information the agent already has access to view.
From the tool's definition Tool name 'getVideoDetails' and description 'Get detailed information about multiple YouTube videos. Returns comprehensive data including video metadata, statistics, and content details.' indicate retrieval of publicly available data with no side effects or…
Attacks that exploit this kind of access
Get detailed information about multiple YouTube videos. Returns comprehensive data including video metadata, statistics, and content details. Use this when you need complete information about specific videos. It is categorised as a Read tool in the Yt MCP Server, which means it retrieves data without modifying state.
Register the Yt MCP server in PolicyLayer and add a rule for getVideoDetails: 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 Yt. Nothing to install.
getVideoDetails 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 getVideoDetails 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 getVideoDetails. 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.
getVideoDetails is provided by the Yt MCP server (yt-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 →