get_dive_tree

Get the full XML-like component tree for a dive session. Shows all registered components in their hierarchy with status, agent assignments, interaction counts, and bug counts. Also returns a Mermaid diagram for visual rendering. Use this for a quick overview of app structure and dive progress.

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/get-dive-tree.md

WHAT IT DOES

What get_dive_tree does on Nodebench

AI agents call get_dive_tree 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 get_dive_tree is rated Low

This tool retrieves and displays structural information about a dive session (components, hierarchy, status, assignments, counts, and a Mermaid diagram). It has no capability to modify, delete, execute commands, or trigger external operations. The blast radius of misuse is minimal—an attacker could only gain visibility into an application's internal structure.

From the tool's definition Tool description explicitly states 'Get the full XML-like component tree' and 'returns' data about registered components, hierarchy, status, and metrics. Verbs used: 'Get', 'shows', 'returns' — all read operations with no data modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_dive_tree Allowed

get_dive_tree 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": {
    "get_dive_tree": {}
  }
}

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 get_dive_tree call is checked against it from then on.

FAQ

Questions about get_dive_tree

What does the get_dive_tree tool do? +

How do I enforce a policy on get_dive_tree? +

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

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

Can I rate-limit get_dive_tree? +

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

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

get_dive_tree 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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