generate_vehicle_assembly · MCP-Blender MCP: Risk & Policy

WHAT IT DOES

What generate_vehicle_assembly does on MCP-Blender

AI agents invoke generate_vehicle_assembly 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 generate_vehicle_assembly needs a policy

This tool executes a complex automated generation process within Blender to produce a full vehicle electrical assembly. It spans Write (creates 3D content) and Execute (triggers external operations in Blender with parametric/relational design).

From the tool's definition 'Generate complete vehicle electrical assembly with wiring' — triggers an automated generation/assembly operation in Blender, creating complex 3D content and wiring structures through external system integration

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_vehicle_assembly Rate-limited

generate_vehicle_assembly 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": {
    "generate_vehicle_assembly": {
      "limits": [
        {
          "counter": "generate_vehicle_assembly_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 generate_vehicle_assembly

What does the generate_vehicle_assembly tool do? +

Generate complete vehicle electrical assembly with wiring. 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 generate_vehicle_assembly? +

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

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

Can I rate-limit generate_vehicle_assembly? +

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

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

generate_vehicle_assembly 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.