blender_batch

A execute tool on the Blender MCP server.

SERVERBlender SOURCEsandraschi/blender-mcp

High RISK CLASS

Category Execute

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-batch.md

WHAT IT DOES

What blender_batch does on Blender

AI agents invoke blender_batch to trigger actions in Blender. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why blender_batch is rated High

The name 'blender_batch' suggests batch processing or execution of multiple Blender operations at once. In the context of a Blender MCP server that controls 3D scenes, batch operations typically execute multiple commands or scripts, which could have wide-ranging effects.

From the tool's definition Tool name is 'blender_batch'; description is empty or uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blender_batch 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_batch, this is the rule to start with:

blender_batch Rate-limited

blender_batch stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_batch": {
      "limits": [
        {
          "counter": "blender_batch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_batch call is checked against it from then on.

FAQ

Questions about blender_batch

What does the blender_batch tool do? +

blender_batch is a execute tool on the Blender MCP server. It is categorised as a Execute tool in the Blender MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on blender_batch? +

Register the Blender MCP server in PolicyLayer and add a rule for blender_batch: 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_batch? +

blender_batch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit blender_batch? +

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

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

blender_batch 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 → High-risk tools on this server →

Across the catalogue

qt_batch on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →