Record a browser session as a video (WebM). Optionally runs a JavaScript
AI agents invoke video to trigger actions in SnapAPI MCP Server. 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 records a browser session and optionally executes arbitrary JavaScript code against a URL. The JavaScript execution capability means it can trigger external operations and run code in a browser context, making it Execute category. High severity because it can run arbitrary JS in a browser session against any URL, with potential for significant side effects.
From the tool's definition Record a browser session as a video (WebM). Optionally runs a JavaScript
Attacks that exploit this kind of access
Record a browser session as a video (WebM). Optionally runs a JavaScript. It is categorised as a Execute tool in the SnapAPI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SnapAPI MCP Server MCP server in PolicyLayer and add a rule for 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 SnapAPI MCP Server. Nothing to install.
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 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 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.
video is provided by the SnapAPI MCP Server MCP server (sleywill/snapapi-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 →