AI agents use save_scene to create or update resources in Godot MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP environment.
This tool creates or modifies data (scene files) in a reversible manner. Changes can be undone through version control or Godot's undo system, making it Write rather than Destructive. The blast radius is medium because corrupted or malicious scene modifications could break game functionality, but the changes are not permanent at the file system level and can be recovered.
From the tool's definition Tool name 'save_scene' and description 'Save changes to a scene file' indicate modification of existing scene files in the Godot project.
Documented attack patterns abuse exactly the kind of access save_scene gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for save_scene:
{
"version": "1",
"default": "deny",
"tools": {
"save_scene": {
"limits": [
{
"counter": "save_scene_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Save changes to a scene file. It is categorised as a Write tool in the Godot MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot 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. 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 server (leesinliang/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Godot MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Godot MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.