scene_save

Save the currently edited scene to its existing path.

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/scene-save.md

WHAT IT DOES

What scene_save does on Breakpoint

AI agents use scene_save 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.

RISK

Why scene_save is rated Medium

This tool creates or modifies data (the saved scene file) in a reversible manner. It writes to an existing path rather than deleting, making it Write rather than Destructive. The severity is medium because saving a scene could overwrite previous work, but the operation is reversible through undo or version control, and the scope is limited to a single scene file.

From the tool's definition Tool name 'scene_save' and description 'Save the currently edited scene to its existing path' indicate the tool modifies and persists data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scene_save 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_save, this is the rule to start with:

scene_save Rate-limited

scene_save 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": {
    "scene_save": {
      "limits": [
        {
          "counter": "scene_save_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 scene_save call is checked against it from then on.

FAQ

Questions about scene_save

What does the scene_save tool do? +

Save the currently edited scene to its existing 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.

How do I enforce a policy on scene_save? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for scene_save: 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 scene_save? +

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

Can I rate-limit scene_save? +

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

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

scene_save 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

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

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