scene_open
Open an existing scene in the editor by res:// path.
This record as markdown: /tools/breakpoint-mcp/scene-open.md
What scene_open does on Breakpoint
AI agents use scene_open 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 | Scene path, e.g. res://scenes/main.tscn |
Parameters from the server's own tool schema.
Why scene_open is rated Medium
Opening a scene in an editor constitutes a state change to the application (the active scene becomes different), making this a Write operation rather than a simple Read. While it doesn't create new data or permanently delete anything, it does modify the current editing context.
From the tool's definition Tool name 'scene_open' combined with description 'Open an existing scene in the editor by res:// path' indicates loading/opening a scene resource, which modifies the editor state and active context.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs scene_open 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 scene_open, this is the rule to start with:
scene_open 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 Breakpoint, apply this rule, and every scene_open call is checked against it from then on.
Questions about scene_open
Open an existing scene in the editor by res:// path. 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.
scene_open accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for scene_open: 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.
scene_open 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_open 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_open. 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_open 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.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue