Save a scene (re-writes it to disk, optionally to a new path).
AI agents use save_scene to create or update resources in Godot Mcp Pilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Mcp Pilot environment.
This tool creates or modifies data reversibly by persisting scene changes to disk storage. It falls under Write rather than Destructive because the operation is reversible (previous versions can typically be recovered via version control or backups, and the tool doesn't inherently delete data).
From the tool's definition The tool description states it 'Save a scene (re-writes it to disk, optionally to a new path)'. The phrase 're-writes it to disk' indicates persistent modification of files in the game project.
Attacks that exploit this kind of access
Save a scene (re-writes it to disk, optionally to a new path). It is categorised as a Write tool in the Godot Mcp Pilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Mcp Pilot 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 Godot Mcp Pilot. 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 Godot Mcp Pilot MCP server (pushks18/godot-mcp-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →