Call a method on a node in the running game.
AI agents invoke call_game_node_method to trigger actions in Godot MCP Server. 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.
This tool executes arbitrary methods on game nodes at runtime. The effects are entirely determined by which method is called and its arguments, potentially triggering any game logic, modifying state, or causing side effects within the running game. This is an Execute-category action with high severity since an AI agent could invoke destructive or unintended game behaviors depending on what methods are available.
From the tool's definition Call a method on a node in the running game
Attacks that exploit this kind of access
Call a method on a node in the running game. It is categorised as a Execute tool in the Godot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for call_game_node_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 MCP Server. Nothing to install.
call_game_node_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 call_game_node_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 call_game_node_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.
call_game_node_method is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →