This record as markdown: /tools/godot-breakpoint-mcp/node-find.md
What node_find does on Godot Breakpoint
AI agents call node_find to retrieve information from Godot Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why node_find is rated Low
This tool retrieves or queries data about nodes in a Godot scene without modifying, executing, or deleting anything. It is a straightforward read operation similar to search, list, or get operations. The low severity reflects that searching for nodes poses minimal risk even if misused by an agent, as it only accesses existing information.
From the tool's definition Tool name is 'node_find' with description 'Search a node'. The verb 'search' indicates a read-only query operation with no side effects or data 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 Godot 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 Godot Breakpoint, apply this rule, and every node_find call is checked against it from then on.
Questions about node_find
Search a node. It is categorised as a Read tool in the Godot Breakpoint MCP Server, which means it retrieves data without modifying state.
Register the Godot 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 Godot 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 Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue