This record as markdown: /tools/chanceflow-godot-mcp/scene-instantiate.md
What scene_instantiate does on Godot
AI agents use scene_instantiate to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
Why scene_instantiate is rated Medium
Based on the tool name, 'scene_instantiate' likely creates a new instance of a scene within the Godot editor or running project, which is a write/create operation. However, with no description available, confidence is reduced. In context of sibling tools (animation_create, autoload_add), this server manages Godot scene/editor state, so instantiation is most likely a reversible creation/write action.
From the tool's definition Tool name 'scene_instantiate' — description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs scene_instantiate 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 scene_instantiate, this is the rule to start with:
scene_instantiate stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 scene_instantiate call is checked against it from then on.
Questions about scene_instantiate
scene_instantiate is a write tool on the Godot MCP server. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP server in PolicyLayer and add a rule for scene_instantiate: 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.
scene_instantiate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the scene_instantiate 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 scene_instantiate. 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.
scene_instantiate is provided by the Godot MCP server (chanceflow/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.
This server
Across the catalogue