get_youtube_videos
AI agents call get_youtube_videos to retrieve information from Mcp Metricool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves YouTube video data from the Metricool API, consistent with the server's purpose of aggregating social media metrics. The 'get_' prefix and pattern match other read-only query tools on the server. While the description is uninformative, the naming convention and context strongly suggest read-only retrieval with no side effects.
From the tool's definition Tool name 'get_youtube_videos' and server context indicate data retrieval. Description is empty, but sibling tools (get_instagram_posts, get_facebook_posts, get_bluesky_posts) follow a consistent 'get_*' pattern for querying social media metrics without…
Attacks that exploit this kind of access
get_youtube_videos. It is categorised as a Read tool in the Mcp Metricool MCP Server, which means it retrieves data without modifying state.
Register the Mcp Metricool MCP server in PolicyLayer and add a rule for get_youtube_videos: 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 Metricool. Nothing to install.
get_youtube_videos 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_youtube_videos 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_youtube_videos. 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_youtube_videos is provided by the Mcp Metricool MCP server (namdzmaso02/mcp-metricool). 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 →