dive_reexplore
Re-traverse a route after code changes to detect regressions and verify fixes. Compares the current state against previously registered components, bugs, and test results for that route. The agent should navigate to the route first (via Playwright), take a fresh snapshot/screenshot, then call thi...
This record as markdown: /tools/io-github-homenshum-nodebench/dive-reexplore.md
What dive_reexplore does on Nodebench
AI agents invoke dive_reexplore 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 dive_reexplore is rated High
This tool triggers browser-based navigation via Playwright (an external browser automation engine), takes screenshots, and performs comparison logic against stored state. It actively executes browser actions and external operations, making it Execute category. The blast radius is high because it can interact with live application routes and may trigger unintended side effects in the application being tested.
From the tool's definition Re-traverse a route after code changes... navigate to the route first (via Playwright), take a fresh snapshot/screenshot, then call this tool... It diffs against the prior state and flags any new issues or confirms fixes.
Attacks that exploit this kind of access
The rule that runs dive_reexplore 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_reexplore, this is the rule to start with:
dive_reexplore 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 dive_reexplore call is checked against it from then on.
Questions about dive_reexplore
Re-traverse a route after code changes to detect regressions and verify fixes. Compares the current state against previously registered components, bugs, and test results for that route. The agent should navigate to the route first (via Playwright), take a fresh snapshot/screenshot, then call this tool with what they observe. It diffs against the prior state and flags any new issues or confirms fixes. 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 dive_reexplore: 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.
dive_reexplore 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 dive_reexplore 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 dive_reexplore. 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.
dive_reexplore 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