Get detailed stats and metadata for a specific YouTube video.
AI agents call youtube_video_details to retrieve information from Mcp Everything 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 data (video statistics and metadata) without side effects. It does not create, modify, delete, or execute anything. It aligns with the 'Read' category as defined: 'retrieves or queries data; no side effects (search, list, get, fetch).' The confidence is high because the description is clear and unambiguous.
From the tool's definition Tool name 'youtube_video_details' and description 'Get detailed stats and metadata for a specific YouTube video' indicate retrieval of publicly available video information with no modification, creation, deletion, or execution of code.
Attacks that exploit this kind of access
Get detailed stats and metadata for a specific YouTube video. It is categorised as a Read tool in the Mcp Everything MCP Server, which means it retrieves data without modifying state.
Register the Mcp Everything MCP server in PolicyLayer and add a rule for youtube_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 Mcp Everything. Nothing to install.
youtube_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 youtube_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 youtube_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.
youtube_video_details is provided by the Mcp Everything MCP server (wellix260/mcp-everything). 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 →