blender_new_file

Create a new blank Blender file (General template). Discards unsaved changes.

SERVERBlender Copilot MCP Server SOURCEdwgx/blender-copilot

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dwgx-blender-copilot/blender-new-file.md

WHAT IT DOES

What blender_new_file does on Blender Copilot MCP Server

AI agents call blender_new_file to permanently remove resources in Blender Copilot MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why blender_new_file is rated Critical

Creating a new blank file irreversibly discards any unsaved work in the current Blender session. This is a destructive action because unsaved changes cannot be recovered once the new file is created.

From the tool's definition Discards unsaved changes

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blender_new_file safely

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

blender_new_file Hidden

blender_new_file is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "blender_new_file"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every blender_new_file call is checked against it from then on.

FAQ

Questions about blender_new_file

What does the blender_new_file tool do? +

Create a new blank Blender file (General template). Discards unsaved changes. It is categorised as a Destructive tool in the Blender Copilot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on blender_new_file? +

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

What risk level is blender_new_file? +

blender_new_file is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit blender_new_file? +

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

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

blender_new_file is provided by the Blender Copilot MCP Server MCP server (dwgx/blender-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Blender Copilot MCP Server, and thousands of servers like it.

This server

All 307 Blender Copilot MCP Server tools → Critical-risk tools on this server →

Across the catalogue

delete_file on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →