node_call_method

Invoke a method on a node in the EDITED scene. DESTRUCTIVE (arbitrary invocation, not undoable) — gated by confirmation.

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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)'.

Questions about node_call_method

What does the node_call_method tool do? +

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.

How do I enforce a policy on node_call_method? +

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.

What risk level is node_call_method? +

node_call_method is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit node_call_method? +

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.

How do I block node_call_method completely? +

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.

What MCP server provides node_call_method? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Godot Breakpoint's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.