This record as markdown: /tools/sbox/save-scene.md
What save_scene does on Sbox
AI agents use save_scene to create or update resources in Sbox, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sbox environment.
Why save_scene is rated Medium
This tool creates or modifies data reversibly by saving scene state. It is a Write action because it persists changes to a file that can be later modified or reverted through normal editor workflows. It is not Destructive because saving is reversible—prior versions can be recovered from version control or backups.
From the tool's definition The tool 'save_scene' persists the currently open scene in the s&box editor. The description explicitly states it 'Save[s] the currently open scene', which modifies the state of the game development project by writing data to disk.
Attacks that exploit this kind of access
The rule that runs save_scene safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_scene, this is the rule to start with:
save_scene 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 Sbox, apply this rule, and every save_scene call is checked against it from then on.
Questions about save_scene
Save the currently open scene in the s&box editor. It is categorised as a Write tool in the Sbox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sbox MCP server in PolicyLayer and add a rule for save_scene: 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 Sbox. Nothing to install.
save_scene 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 save_scene 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 save_scene. 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.
save_scene is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sbox, and thousands of servers like it.
This server
Across the catalogue