runtime_call_method
Call a method on a node in the running game.
This record as markdown: /tools/yanhuifair-godot-mcp/runtime-call-method.md
What runtime_call_method does on Godot
AI agents invoke runtime_call_method to trigger actions in Godot. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
args | object | — | Positional arguments. |
path | string | Yes | Node path inside the running scene. |
method | string | Yes | Method name to call on the node. |
Parameters from the server's own tool schema.
Why runtime_call_method is rated High
Executes arbitrary methods on live game nodes, with unpredictable side effects.
From the tool's definition Call a method on a node in the running game
Risk signalsAccepts file system path (path)
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, 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, apply this rule, and every runtime_call_method call is checked against it from then on.
Questions about runtime_call_method
Call a method on a node in the running game. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
runtime_call_method accepts 3 parameters: args, path, method. Required: path, method. The full parameter table on this page comes from the server's own tool schema.
Register the Godot 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. 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 MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
Across the catalogue