scene_pack
Save a node branch (the node and its subtree) as a new PackedScene file. DESTRUCTIVE (writes a file) — gated by confirmation. Does not modify the edited scene.
This record as markdown: /tools/breakpoint-mcp/scene-pack.md
What scene_pack does on Breakpoint
AI agents use scene_pack 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 | Branch root node path relative to the scene root |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
to_path | string | Yes | Where to save the PackedScene, e.g. res://scenes/branch.tscn |
Parameters from the server's own tool schema.
Why scene_pack is rated Medium
This tool creates a new file (PackedScene) which is a reversible Write operation. Although the description includes 'DESTRUCTIVE', the actual behavior—saving/exporting data to a new file without deleting existing data—is Write-category. The tool is gated by confirmation, further reducing risk.
From the tool's definition Tool description states it 'Save[s] a node branch...as a new PackedScene file' and explicitly notes '(writes a file)'. The term 'Save' and 'writes a file' indicate data creation/modification.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs scene_pack 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_pack, this is the rule to start with:
scene_pack 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_pack call is checked against it from then on.
Questions about scene_pack
Save a node branch (the node and its subtree) as a new PackedScene file. DESTRUCTIVE (writes a file) — gated by confirmation. Does not modify the edited scene. 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_pack accepts 3 parameters: path, confirm, to_path. Required: path, to_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_pack: 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_pack 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_pack 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_pack. 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_pack 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