Create a new Blender scene with the specified name.
AI agents use create_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.
This tool creates new data (a Blender scene) in a reversible manner. It does not execute arbitrary code, delete data, or cause financial transactions. Scene creation can be undone in Blender, making it a Write operation rather than Destructive. The blast radius is minimal since creating an unused scene has no side effects on existing work or external systems.
From the tool's definition Tool creates a new Blender scene with a specified name. The verb 'create' and the action of instantiating a new scene object indicates data creation.
Documented attack patterns abuse exactly the kind of access create_scene gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Blender, and nothing reaches the server without passing your rules. This is the rule we recommend for create_scene:
{
"version": "1",
"default": "deny",
"tools": {
"create_scene": {
"limits": [
{
"counter": "create_scene_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Create a new Blender scene with the specified name. 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.
Register the Blender MCP server in PolicyLayer and add a rule for create_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.
create_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 create_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 create_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.
create_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.
Start from Blender, 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.
77 Blender tools catalogued and risk-classified — across an index of 43,000+ MCP servers.