capture_ui_screenshot

Capture a screenshot of a URL using headless Playwright. Returns the screenshot as an inline image that multimodal agents can see and evaluate directly. Also captures browser console errors. Supports viewport presets (mobile/tablet/desktop/wide) or custom dimensions. Requires Playwright to be ins...

SERVERNodebench SOURCEnodebench-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/capture-ui-screenshot.md

What capture_ui_screenshot does on Nodebench

AI agents invoke capture_ui_screenshot 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 capture_ui_screenshot is rated High

This tool executes a headless browser (Playwright) to navigate to an arbitrary URL and capture screenshots. It triggers external operations (browser automation, network requests to arbitrary URLs) whose effects depend on arguments.

From the tool's definition Capture a screenshot of a URL using headless Playwright... Also captures browser console errors.

Questions about capture_ui_screenshot

What does the capture_ui_screenshot tool do? +

Capture a screenshot of a URL using headless Playwright. Returns the screenshot as an inline image that multimodal agents can see and evaluate directly. Also captures browser console errors. Supports viewport presets (mobile/tablet/desktop/wide) or custom dimensions. Requires Playwright to be installed in the project. 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.

How do I enforce a policy on capture_ui_screenshot? +

Register the Nodebench MCP server in PolicyLayer and add a rule for capture_ui_screenshot: 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.

What risk level is capture_ui_screenshot? +

capture_ui_screenshot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit capture_ui_screenshot? +

Yes. Add a rate_limit block to the capture_ui_screenshot 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.

How do I block capture_ui_screenshot completely? +

Set action: deny in the PolicyLayer policy for capture_ui_screenshot. 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.

What MCP server provides capture_ui_screenshot? +

capture_ui_screenshot 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nodebench's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.