Stop video recording and save the file (see browser_docs)
AI agents use browser_stop_video_recording to create or update resources in Browser MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Browser MCP Server environment.
This tool stops an ongoing recording session and saves the resulting video file to disk. It creates/writes a new file, which is a reversible write operation. It does not delete data or execute arbitrary code, though misuse could capture sensitive screen content. Severity is medium because the saved file could contain sensitive information captured during the browser session.
From the tool's definition Stop video recording and save the file
Attacks that exploit this kind of access
Stop video recording and save the file (see browser_docs). It is categorised as a Write tool in the Browser MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Browser MCP Server MCP server in PolicyLayer and add a rule for browser_stop_video_recording: 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 Browser MCP Server. Nothing to install.
browser_stop_video_recording is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the browser_stop_video_recording 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_recording. 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_recording is provided by the Browser MCP Server MCP server (madebytokens/browser-mcp-server). 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 →