browser_stop_video
AI agents invoke browser_stop_video to trigger actions in Playwright MCP. 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 a browser operation (stopping video) whose effects depend on the current page state and could have externally observable consequences (interrupting media playback, affecting user experience, or triggering page-specific handlers).
From the tool's definition Tool name 'browser_stop_video' suggests stopping video playback in a browser context. The parent server provides 'browser automation capabilities' and the sibling tools perform actions like click, drag, and evaluate, indicating this tool executes browser…
Attacks that exploit this kind of access
browser_stop_video. It is categorised as a Execute tool in the Playwright MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_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 Playwright MCP. Nothing to install.
browser_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 browser_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 browser_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.
browser_stop_video is provided by the Playwright MCP server (naumana3services-maker/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 →