burst_capture
Capture N sequential screenshots at fixed intervals using Playwright.
This record as markdown: /tools/io-github-homenshum-nodebench/burst-capture.md
What burst_capture does on Nodebench
AI agents invoke burst_capture to trigger actions in Nodebench. 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.
Why burst_capture is rated High
This tool executes browser automation using Playwright, an external process that controls a browser. It repeatedly triggers external operations (screenshot captures) at fixed intervals, qualifying as Execute. Misuse could lead to unintended scraping of sensitive pages, resource exhaustion from repeated captures, or capture of confidential browser sessions.
From the tool's definition 'Capture N sequential screenshots at fixed intervals using Playwright' — triggers browser automation via Playwright to perform repeated screenshot capture operations
Attacks that exploit this kind of access
The rule that runs burst_capture safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For burst_capture, this is the rule to start with:
burst_capture 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every burst_capture call is checked against it from then on.
Questions about burst_capture
Capture N sequential screenshots at fixed intervals using Playwright. It is categorised as a Execute tool in the Nodebench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nodebench MCP server in PolicyLayer and add a rule for burst_capture: 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 Nodebench. Nothing to install.
burst_capture 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 burst_capture 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 burst_capture. 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.
burst_capture is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
Across the catalogue