Add a video to the end of the current playback queue without interrupting what is playing. If nothing is playing, starts playback.
AI agents invoke queue_video to trigger actions in Social Video. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation — controlling the mpv media player by queuing and potentially starting video playback. It doesn't just read or write data; it executes a player action with real-world effects (media playback), placing it in the Execute category.
From the tool's definition Add a video to the end of the current playback queue without interrupting what is playing. If nothing is playing, starts playback.
Attacks that exploit this kind of access
Add a video to the end of the current playback queue without interrupting what is playing. If nothing is playing, starts playback. It is categorised as a Execute tool in the Social Video MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Social Video MCP server in PolicyLayer and add a rule for queue_video: 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.
queue_video is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the queue_video 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 queue_video. 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.
queue_video 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 →