node_call_method
Invoke a method on a node in the EDITED scene. DESTRUCTIVE (arbitrary invocation, not undoable) — gated by confirmation.
This record as markdown: /tools/godot-breakpoint-mcp/node-call-method.md
What node_call_method does on Godot Breakpoint
AI agents invoke node_call_method to trigger actions in Godot Breakpoint. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why node_call_method is rated High
Although the description mentions 'DESTRUCTIVE' and 'not undoable', the primary action is method invocation (Execute category). The destructiveness depends on which method is called—this is a code execution primitive. The gating by confirmation slightly mitigates risk but does not change the fundamental capability.
From the tool's definition Tool description explicitly states 'Invoke a method on a node' and warns 'DESTRUCTIVE (arbitrary invocation, not undoable)'.
Attacks that exploit this kind of access
The rule that runs node_call_method 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_call_method, this is the rule to start with:
node_call_method stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_call_method call is checked against it from then on.
Questions about node_call_method
Invoke a method on a node in the EDITED scene. DESTRUCTIVE (arbitrary invocation, not undoable) — gated by confirmation. It is categorised as a Execute tool in the Godot Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for node_call_method: 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_call_method is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the node_call_method 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_call_method. 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_call_method 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.
Across the catalogue