game_spawn_node
Cria no dinamicamente no jogo.
This record as markdown: /tools/mcp-godot-desenvolvimento/game-spawn-node.md
What game_spawn_node does on Mcp Godot Desenvolvimento
AI agents invoke game_spawn_node to trigger actions in Mcp Godot Desenvolvimento. 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 game_spawn_node is rated High
This tool creates nodes dynamically at game runtime, which constitutes executing an operation that modifies the live game state. Runtime node spawning can have wide-ranging side effects depending on what node is spawned (scripts, physics bodies, etc.), making it an Execute-category action with high severity due to potential for misuse in a running game environment.
From the tool's definition 'Cria no dinamicamente no jogo' — dynamically spawns/creates a node at runtime in the game
Attacks that exploit this kind of access
The rule that runs game_spawn_node safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Godot Desenvolvimento, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For game_spawn_node, this is the rule to start with:
game_spawn_node 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 Mcp Godot Desenvolvimento, apply this rule, and every game_spawn_node call is checked against it from then on.
Questions about game_spawn_node
Cria no dinamicamente no jogo. It is categorised as a Execute tool in the Mcp Godot Desenvolvimento MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Godot Desenvolvimento MCP server in PolicyLayer and add a rule for game_spawn_node: 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 Mcp Godot Desenvolvimento. Nothing to install.
game_spawn_node 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 game_spawn_node 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 game_spawn_node. 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.
game_spawn_node is provided by the Mcp Godot Desenvolvimento MCP server (joabcostamd/mcp-godot-desenvolvimento). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Godot Desenvolvimento, and thousands of servers like it.
Across the catalogue