blender_scene

A write tool on the Blender MCP server.

SERVERBlender SOURCEsandraschi/blender-mcp

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/sandraschi-blender-mcp/blender-scene.md

WHAT IT DOES

What blender_scene does on Blender

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

RISK

Why blender_scene is rated Medium

Based on the server context of AI-powered Blender control and sibling tools that create/manipulate 3D scenes, 'blender_scene' likely manages scene-level operations (create, modify, configure scenes). Without a description, this is speculative. Scene manipulation in Blender can span Read to Destructive, but Write is the most probable default for a scene management tool. Confidence is low due to empty description.

From the tool's definition Tool name is 'blender_scene'; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blender_scene safely

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

blender_scene Rate-limited

blender_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_scene": {
      "limits": [
        {
          "counter": "blender_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 Blender, apply this rule, and every blender_scene call is checked against it from then on.

FAQ

Questions about blender_scene

What does the blender_scene tool do? +

blender_scene is a write tool on the Blender MCP server. It is categorised as a Write tool in the Blender 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_scene? +

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

What risk level is blender_scene? +

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

Can I rate-limit blender_scene? +

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

Set action: deny in the PolicyLayer policy for blender_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_scene? +

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

KEEP EXPLORING

More on Blender, and thousands of servers like it.

This server

All 81 Blender tools →

Across the catalogue

The MCP Attack Database →

Guides

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