深度分析单个 YouTube Shorts 视频的表现。
AI agents call analyze_video_potential to retrieve information from Viral Shorts 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 existing video performance data (likely Views Per Hour, engagement metrics, etc.) from YouTube Data API without modifying, deleting, or executing external operations. It is a read-only analytical tool with no side effects, making it a standard 'Read' category tool with low severity risk.
From the tool's definition Tool performs 'deep analysis' of individual YouTube Shorts video performance. The description uses 'analyze' and 'performance' metrics, indicating data retrieval and querying operations.
Attacks that exploit this kind of access
深度分析单个 YouTube Shorts 视频的表现。. It is categorised as a Read tool in the Viral Shorts MCP Server, which means it retrieves data without modifying state.
Register the Viral Shorts MCP server in PolicyLayer and add a rule for analyze_video_potential: 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 Viral Shorts. Nothing to install.
analyze_video_potential 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 analyze_video_potential 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 analyze_video_potential. 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.
analyze_video_potential is provided by the Viral Shorts MCP server (xeron2000/viral-shorts). 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 →