batch_generate_components · MCP-Blender MCP: Risk & Policy

WHAT IT DOES

What batch_generate_components does on MCP-Blender

AI agents invoke batch_generate_components to trigger actions in MCP-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.

WHY IT NEEDS A POLICY

Why batch_generate_components needs a policy

This tool executes batch operations in Blender to generate multiple components, which constitutes triggering external operations (in the Blender environment) at scale. The batch nature increases the blast radius since misuse could flood the scene with many unwanted objects.

From the tool's definition 'Generate multiple components from a specification list' — batch generation of multiple 3D components triggers external Blender operations whose scope and effects depend on the specification list arguments

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_generate_components Rate-limited

batch_generate_components 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": {
    "batch_generate_components": {
      "limits": [
        {
          "counter": "batch_generate_components_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP-Blender, so you can run agents against it safely.

FAQ

Questions about batch_generate_components

What does the batch_generate_components tool do? +

Generate multiple components from a specification list. It is categorised as a Execute tool in the MCP-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 batch_generate_components? +

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

What risk level is batch_generate_components? +

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

Can I rate-limit batch_generate_components? +

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

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

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