nb_view_screenshots
Get captured route screenshots for visual QA.
This record as markdown: /tools/io-github-homenshum-nodebench/nb-view-screenshots.md
What nb_view_screenshots does on Nodebench
AI agents call nb_view_screenshots to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why nb_view_screenshots is rated Low
This tool retrieves existing screenshot data for quality assurance purposes. The verb 'Get' and 'view' indicate read-only access to stored visual artifacts. There is no capability to modify, delete, execute code, or trigger external operations. The blast radius of misuse is minimal—an agent could retrieve screenshots it shouldn't access, but no data would be harmed or altered.
From the tool's definition Tool name contains 'view' and description states 'Get captured route screenshots' — purely a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs nb_view_screenshots 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 nb_view_screenshots, this is the rule to start with:
nb_view_screenshots is read-only, so it stays allowed. 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 nb_view_screenshots call is checked against it from then on.
Questions about nb_view_screenshots
Get captured route screenshots for visual QA. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for nb_view_screenshots: 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.
nb_view_screenshots is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the nb_view_screenshots 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 nb_view_screenshots. 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.
nb_view_screenshots 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.
This server
Across the catalogue