# save_blend_file

Save the current Blender scene to a .blend file

Agent View of the PolicyLayer registry record for `save_blend_file`. HTML page: https://policylayer.com/tools/aryeon0228-blendermcp/save-blend-file

## Facts

- Tool: `save_blend_file`
- Server: BlenderMCP (`aryeon0228/blendermcp`) — https://policylayer.com/tools/aryeon0228-blendermcp.md
- Homepage: https://github.com/Aryeon0228/BlenderMCP
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "save_blend_file",
    "arguments": {}
  }
}
```

## Why save_blend_file is rated Medium

This tool creates or modifies a file on the user's filesystem by serializing the current Blender scene state. While reversible (files can be edited or deleted manually), it commits data to storage and could overwrite existing .blend files if not carefully used. The impact is scoped to file I/O rather than system-wide operations, making it Write rather than Execute.

From the tool's own definition: "Tool name 'save_blend_file' and description 'Save the current Blender scene to a .blend file' indicate data persistence to disk."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches BlenderMCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_blend_file": {
      "limits": [
        {
          "counter": "save_blend_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on BlenderMCP (11)

- `delete_object` — Destructive — https://policylayer.com/tools/aryeon0228-blendermcp/delete-object.md
- `execute_blender_code` — Execute — https://policylayer.com/tools/aryeon0228-blendermcp/execute-blender-code.md
- `render_scene` — Execute — https://policylayer.com/tools/aryeon0228-blendermcp/render-scene.md
- `scale_object` — Execute — https://policylayer.com/tools/aryeon0228-blendermcp/scale-object.md
- `get_object_info` — Read — https://policylayer.com/tools/aryeon0228-blendermcp/get-object-info.md
- `get_scene_info` — Read — https://policylayer.com/tools/aryeon0228-blendermcp/get-scene-info.md
- `get_viewport_screenshot` — Read — https://policylayer.com/tools/aryeon0228-blendermcp/get-viewport-screenshot.md
- `create_object` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/create-object.md
- `move_object` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/move-object.md
- `rotate_object` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/rotate-object.md
- `set_material` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/set-material.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=aryeon0228-blendermcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/aryeon0228-blendermcp