node_get_children
List the direct children of a node (name, type, path). Read-only.
This record as markdown: /tools/breakpoint-mcp/node-get-children.md
What node_get_children does on Breakpoint
AI agents call node_get_children to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Node path relative to the scene root; "." for the root |
Parameters from the server's own tool schema.
Why node_get_children is rated Low
This tool retrieves hierarchical structure information about nodes without modifying any data. The explicit 'Read-only' designation confirms it has no side effects. It is a simple data retrieval operation with minimal security impact.
From the tool's definition Tool name is 'node_get_children' and description explicitly states 'List the direct children of a node (name, type, path). Read-only.'
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs node_get_children safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For node_get_children, this is the rule to start with:
node_get_children 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 Breakpoint, apply this rule, and every node_get_children call is checked against it from then on.
Questions about node_get_children
List the direct children of a node (name, type, path). Read-only. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
node_get_children accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for node_get_children: 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 Breakpoint. Nothing to install.
node_get_children 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 node_get_children 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 node_get_children. 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.
node_get_children is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue