node_find
Search a node's descendants by class and/or name substring (case-insensitive). Read-only.
This record as markdown: /tools/breakpoint-mcp/node-find.md
What node_find does on Breakpoint
AI agents call node_find 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 |
|---|---|---|---|
type | string | — | Only match nodes of this class (is_class), e.g. Sprite2D |
limit | integer | — | Max matches to return (default 200) |
root_path | string | — | Where to search from; "." or omitted for the scene root |
name_contains | string | — | Only match nodes whose name contains this substring |
Parameters from the server's own tool schema.
Why node_find is rated Low
This tool retrieves information about node hierarchy through search operations with no capability to modify, delete, or execute actions. It is a straightforward query operation with no side effects, matching the Read category definition.
From the tool's definition Tool description explicitly states 'Read-only' and the function searches/queries node descendants by class and name substring without modification.
Attacks that exploit this kind of access
The rule that runs node_find 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_find, this is the rule to start with:
node_find 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_find call is checked against it from then on.
Questions about node_find
Search a node's descendants by class and/or name substring (case-insensitive). Read-only. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
node_find accepts 4 parameters: type, limit, root_path, name_contains. 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_find: 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_find 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_find 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_find. 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_find 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