scene_save_as
Save the current scene to a new res:// path (Save As). DESTRUCTIVE (writes a file) — gated by confirmation.
This record as markdown: /tools/godot-breakpoint-mcp/scene-save-as.md
What scene_save_as does on Godot Breakpoint
AI agents use scene_save_as to create or update resources in Godot Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Breakpoint environment.
Why scene_save_as is rated Medium
This tool writes/creates a file at a new path, which is a Write operation. While the description labels it 'DESTRUCTIVE,' it saves to a new path (Save As) rather than overwriting existing data irreversibly — it creates a new file. However, it could overwrite an existing file at the target path, which raises severity to high. The confirmation gate reduces but doesn't eliminate risk.
From the tool's definition 'Save the current scene to a new res:// path (Save As)' and 'writes a file'
Attacks that exploit this kind of access
The rule that runs scene_save_as safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scene_save_as, this is the rule to start with:
scene_save_as 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 Godot Breakpoint, apply this rule, and every scene_save_as call is checked against it from then on.
Questions about scene_save_as
Save the current scene to a new res:// path (Save As). DESTRUCTIVE (writes a file) — gated by confirmation. It is categorised as a Write tool in the Godot Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for scene_save_as: 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 Godot Breakpoint. Nothing to install.
scene_save_as 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_save_as 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_save_as. 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_save_as is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue