AI agents invoke browser_video_enable 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 an external operation (activating video recording) within the browser automation context. It doesn't merely read data, but initiates a recording process that captures browser session activity. This is an Execute-level action as it starts a recording operation whose effects depend on subsequent browser interactions.
From the tool's definition 브라우저 세션의 비디오 녹화 기능을 활성화합니다 (Enables video recording functionality for the browser session)
Documented attack patterns abuse exactly the kind of access browser_video_enable gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_video_enable:
{
"version": "1",
"default": "deny",
"tools": {
"browser_video_enable": {
"limits": [
{
"counter": "browser_video_enable_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_video_enable stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
브라우저 세션의 비디오 녹화 기능을 활성화합니다. 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_video_enable: 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_video_enable 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_video_enable 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_video_enable. 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_video_enable is provided by the Playwright MCP server (korwabs/playwright-record-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 Playwright MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.