runtime_call_method
Invoke a method on a live node. DESTRUCTIVE (arbitrary invocation) — gated by confirmation. Args use the tagged-Variant convention.
This record as markdown: /tools/godot-breakpoint-mcp/runtime-call-method.md
What runtime_call_method does on Godot Breakpoint
AI agents invoke runtime_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 runtime_call_method is rated High
This tool executes arbitrary methods on live Godot nodes at runtime. While the description labels it 'DESTRUCTIVE' and includes confirmation gating as a safeguard, the primary capability is method invocation rather than irreversible deletion.
From the tool's definition Tool description states 'Invoke a method on a live node' with explicit warning 'DESTRUCTIVE (arbitrary invocation)' and notes confirmation gating. The 'arbitrary invocation' language indicates the tool can execute any method the Godot runtime exposes.
Attacks that exploit this kind of access
The rule that runs runtime_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 runtime_call_method, this is the rule to start with:
runtime_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 runtime_call_method call is checked against it from then on.
Questions about runtime_call_method
Invoke a method on a live node. DESTRUCTIVE (arbitrary invocation) — gated by confirmation. Args use the tagged-Variant convention. 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 runtime_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.
runtime_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 runtime_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 runtime_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.
runtime_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