blender.save_scene

Save the active Blender scene

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/blender.save-scene.md

WHAT IT DOES

What blender.save_scene does on CoWork OS

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

RISK

Why blender.save_scene is rated Medium

This tool creates or modifies data reversibly by saving scene state to storage. While it doesn't delete data, it overwrites existing scene files, which could result in loss of previous versions if not managed carefully. The severity is medium because the blast radius is localized to the user's Blender project files and doesn't affect external systems, financial assets, or allow arbitrary code execution.

From the tool's definition Tool description states 'Save the active Blender scene', which is a write operation that modifies/persists data (the scene file).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blender.save_scene safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender.save_scene, this is the rule to start with:

blender.save_scene Rate-limited

blender.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": {
    "blender.save_scene": {
      "limits": [
        {
          "counter": "blender.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 CoWork OS, apply this rule, and every blender.save_scene call is checked against it from then on.

FAQ

Questions about blender.save_scene

What does the blender.save_scene tool do? +

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

How do I enforce a policy on blender.save_scene? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for blender.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 CoWork OS. Nothing to install.

What risk level is blender.save_scene? +

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

Can I rate-limit blender.save_scene? +

Yes. Add a rate_limit block to the blender.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 blender.save_scene completely? +

Set action: deny in the PolicyLayer policy for blender.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 blender.save_scene? +

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

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

The MCP Attack Database →

Guides

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