add_scene_instance · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_scene_instance does on Godot MCP Server

AI agents use add_scene_instance to create or update resources in Godot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Server environment.

WHY IT NEEDS A POLICY

Why add_scene_instance needs a policy

This tool creates (instantiates) a scene object in the editor, modifying the project by adding data to the scene hierarchy. It is a Write operation because it creates new content reversibly. The severity is high because misuse could add unwanted complexity to a game project, corrupt scene structure, or introduce unintended game elements, but the effect is reversible (unlike Destructive).

From the tool's definition The tool name and description explicitly state 'Instance an existing scene into the currently open scene,' which creates a new node/object in the scene hierarchy.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_scene_instance Rate-limited

add_scene_instance 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_scene_instance": {
      "limits": [
        {
          "counter": "add_scene_instance_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot MCP Server, so you can run agents against it safely.

FAQ

Questions about add_scene_instance

What does the add_scene_instance tool do? +

Instance an existing scene into the currently open scene. It is categorised as a Write tool in the Godot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_scene_instance? +

Register the Godot MCP Server MCP server in PolicyLayer and add a rule for add_scene_instance: 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.

What risk level is add_scene_instance? +

add_scene_instance is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_scene_instance? +

Yes. Add a rate_limit block to the add_scene_instance 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.

How do I block add_scene_instance completely? +

Set action: deny in the PolicyLayer policy for add_scene_instance. 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.

What MCP server provides add_scene_instance? +

add_scene_instance 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.