dive_generate_tests
Generate Playwright regression test code from dive findings. Creates test cases from: bugs (verify the fix holds), interaction tests (replay the sequence), design issues (visual regression checks), and component assertions (verify component presence). The generated code can be saved to a test fil...
This record as markdown: /tools/io-github-homenshum-nodebench/dive-generate-tests.md
What dive_generate_tests does on Nodebench
AI agents use dive_generate_tests to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why dive_generate_tests is rated Medium
This tool creates new test file artifacts (Playwright code) based on dive findings, which is a reversible write operation. It does not execute tests (which would be Execute), delete anything (Destructive), or modify production data. However, the confidence is slightly reduced because the description cuts off mid-sentence ('run with'), leaving some ambiguity about whether execution is included.
From the tool's definition Generates and creates test code artifacts ('Creates test cases', 'can be saved to a test file'). The description explicitly states code generation and file-saving capability.
Attacks that exploit this kind of access
The rule that runs dive_generate_tests 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_generate_tests, this is the rule to start with:
dive_generate_tests stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_generate_tests call is checked against it from then on.
Questions about dive_generate_tests
Generate Playwright regression test code from dive findings. Creates test cases from: bugs (verify the fix holds), interaction tests (replay the sequence), design issues (visual regression checks), and component assertions (verify component presence). The generated code can be saved to a test file and run with. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for dive_generate_tests: 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_generate_tests is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dive_generate_tests 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_generate_tests. 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_generate_tests 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