Stop the currently playing video and close the mpv window.
AI agents invoke stop_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 executes a command against an external system (mpv player) to change its state. While the action itself is reversible and low-impact (simply stopping playback and closing a window), it represents active control and execution of operations rather than passive data retrieval.
From the tool's definition Tool performs 'stop the currently playing video and close the mpv window' — an action that triggers external operations (mpv player control) whose effects depend on the current state of the application.
Attacks that exploit this kind of access
Stop the currently playing video and close the mpv window. 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 stop_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.
stop_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 stop_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 stop_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.
stop_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 →