scene_reload
Reload a scene from disk, discarding unsaved changes to it. DESTRUCTIVE — gated by confirmation. Defaults to the current scene.
This record as markdown: /tools/breakpoint-mcp/scene-reload.md
What scene_reload does on Breakpoint
AI agents call scene_reload to permanently remove resources in Breakpoint, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | — | Scene res:// path; omitted = the current edited scene |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
Parameters from the server's own tool schema.
Why scene_reload is rated Critical
The tool explicitly discards unsaved changes and is self-labeled DESTRUCTIVE. Reloading from disk irreversibly overwrites any in-memory modifications that haven't been saved, making it a destructive operation with high blast radius if triggered unintentionally.
From the tool's definition Reload a scene from disk, discarding unsaved changes to it. DESTRUCTIVE — gated by confirmation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs scene_reload 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_reload, this is the rule to start with:
scene_reload is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every scene_reload call is checked against it from then on.
Questions about scene_reload
Reload a scene from disk, discarding unsaved changes to it. DESTRUCTIVE — gated by confirmation. Defaults to the current scene. It is categorised as a Destructive tool in the Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
scene_reload accepts 2 parameters: path, confirm. 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_reload: 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_reload is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the scene_reload 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_reload. 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_reload 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.
Across the catalogue