save_scene

Save current scene

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

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/caravanglory-cocos-mcp-server/save-scene.md

WHAT IT DOES

What save_scene does on Cocos

AI agents use save_scene to create or update resources in Cocos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cocos environment.

RISK

Why save_scene is rated Medium

This tool modifies and persists scene state by saving changes to disk. While the operation is reversible (scenes can be reverted or re-edited), it commits data changes and affects the project's saved state, making it a Write operation rather than Read.

From the tool's definition Tool description 'Save current scene' indicates persistent modification of scene data. The save operation commits changes to the editor state and underlying scene files, which is a reversible write operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs save_scene safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cocos, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_scene": {
      "limits": [
        {
          "counter": "save_scene_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 Cocos, apply this rule, and every save_scene call is checked against it from then on.

FAQ

Questions about save_scene

What does the save_scene tool do? +

Save current scene. It is categorised as a Write tool in the Cocos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_scene? +

Register the Cocos 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 Cocos. Nothing to install.

What risk level is save_scene? +

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

Can I rate-limit save_scene? +

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.

How do I block save_scene completely? +

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.

What MCP server provides save_scene? +

save_scene is provided by the Cocos MCP server (caravanglory/cocos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cocos, and thousands of servers like it.

This server

All 157 Cocos tools →

Across the catalogue

save_snapshot on Why Did You Render →save_tags on Mcptube Vision → The MCP Attack Database →

Guides

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