Checks a video
AI agents call get_video_seo_score to retrieve information from Youtube-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes SEO metrics for a video without modifying, deleting, or executing external operations. It fits the Read category as a query/analysis function that has no side effects on YouTube data or infrastructure.
From the tool's definition Tool name 'get_video_seo_score' and context ('Checks a video') indicates data retrieval. Sibling tools like 'get_channel_overview', 'get_engagement_stats', and 'get_tag_analysis' confirm this server's pattern of read-only analytics and extraction operations…
Attacks that exploit this kind of access
Checks a video. It is categorised as a Read tool in the Youtube-MCP MCP Server, which means it retrieves data without modifying state.
Register the Youtube- MCP server in PolicyLayer and add a rule for get_video_seo_score: 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-MCP. Nothing to install.
get_video_seo_score 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_video_seo_score 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_video_seo_score. 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_video_seo_score is provided by the Youtube- MCP server (yashkashte5/youtube-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 →