dive_snapshot

SERVERNodebench SOURCEnodebench-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/dive-snapshot.md

WHAT IT DOES

What dive_snapshot does on Nodebench

AI agents call dive_snapshot 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.

RISK

Why dive_snapshot is rated Low

This tool only reads/captures the current state of a page (screenshot or accessibility snapshot) without modifying any data or triggering side effects. It is a passive observation tool used to document UI state.

From the tool's definition Capture a screenshot or accessibility snapshot of the current page... Returns the screenshot as an inline image... or an accessibility tree as text

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dive_snapshot 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 dive_snapshot, this is the rule to start with:

dive_snapshot Allowed

dive_snapshot is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dive_snapshot": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every dive_snapshot call is checked against it from then on.

FAQ

Questions about dive_snapshot

What does the dive_snapshot tool do? +

Capture a screenshot or accessibility snapshot of the current page during a dive session. Requires the built-in Playwright browser to be active (launched by start_ui_dive). Returns the screenshot as an inline image for multimodal agents, or an accessibility tree as text. Use this to capture visual evidence of bugs or document the current state of a component. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dive_snapshot? +

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

dive_snapshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dive_snapshot? +

Yes. Add a rate_limit block to the dive_snapshot 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 dive_snapshot completely? +

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

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

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →