List recent Shorts from a specific YouTube channel.
AI agents call get_channel_shorts to retrieve information from Social Video without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about YouTube Shorts from a channel—a straightforward read operation. The verb 'List' and the passive data retrieval nature confirm it has no side effects, creates no resources, executes no commands, and causes no irreversible changes. The scope is limited to public or authenticated video metadata, making the blast radius low even in a misuse scenario.
From the tool's definition Tool name 'get_channel_shorts' combined with description 'List recent Shorts from a specific YouTube channel' indicates data retrieval with no modification or execution of code.
Attacks that exploit this kind of access
List recent Shorts from a specific YouTube channel. It is categorised as a Read tool in the Social Video MCP Server, which means it retrieves data without modifying state.
Register the Social Video MCP server in PolicyLayer and add a rule for get_channel_shorts: 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 Social Video. Nothing to install.
get_channel_shorts 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_channel_shorts 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_channel_shorts. 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_channel_shorts is provided by the Social Video MCP server (ronantakizawa/social-video-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 →