node_set_editable_instance

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/node-set-editable-instance.md

WHAT IT DOES

What node_set_editable_instance does on Breakpoint

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

Parameter	Type	Required	Description
`path`	string	Yes	Node path of the instanced sub-scene, relative to the scene root
`editable`	boolean	—	Enable (true, default) or disable editable children

Parameters from the server's own tool schema.

RISK

Why node_set_editable_instance is rated Medium

This tool modifies scene configuration and data persistence by toggling editability flags and serializing property overrides. While marked undoable (reducing severity below Execute/Destructive), it reversibly changes how scene data is stored and structured. It does not delete data, execute arbitrary code, or move assets irreversibly, so Write is the appropriate category.

From the tool's definition Tool description states it toggles 'Editable Children' and enables 'property overrides on the instance's internal nodes' to 'serialize into the saved scene', which are modifications to scene data.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs node_set_editable_instance safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For node_set_editable_instance, this is the rule to start with:

node_set_editable_instance Rate-limited

node_set_editable_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": {
    "node_set_editable_instance": {
      "limits": [
        {
          "counter": "node_set_editable_instance_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every node_set_editable_instance call is checked against it from then on.

FAQ

Questions about node_set_editable_instance

What does the node_set_editable_instance tool do? +

Toggle "Editable Children" on an instanced sub-scene (undoable). When enabled, property overrides on the instance's internal nodes serialize into the saved scene; without it the sub-scene is sealed and its internals revert on reload. This is what lets author-time edits (e.g. card_instance slot data) be baked into the .tscn. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does node_set_editable_instance accept? +

node_set_editable_instance accepts 2 parameters: path, editable. Required: path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on node_set_editable_instance? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for node_set_editable_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 Breakpoint. Nothing to install.

What risk level is node_set_editable_instance? +

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

Can I rate-limit node_set_editable_instance? +

Yes. Add a rate_limit block to the node_set_editable_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 node_set_editable_instance completely? +

Set action: deny in the PolicyLayer policy for node_set_editable_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 node_set_editable_instance? +

node_set_editable_instance is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 274 Breakpoint tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →