generate_from_description · MCP-Blender MCP: Risk & Policy

WHAT IT DOES

What generate_from_description does on MCP-Blender

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

This tool takes a natural language description and drives an AI system to execute Blender operations, generating 3D models. The effects depend entirely on the input description, and the tool interacts with an external application (Blender) to produce outputs. This is an execution of external operations rather than a simple write, as it involves AI inference and programmatic Blender control.

From the tool's definition 'Generate 3D model from text description using AI' — triggers an AI-driven generation process that executes operations in Blender to create 3D content

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_from_description Rate-limited

generate_from_description 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_from_description": {
      "limits": [
        {
          "counter": "generate_from_description_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_from_description

What does the generate_from_description tool do? +

Generate 3D model from text description using AI. 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_from_description? +

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

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

Can I rate-limit generate_from_description? +

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

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

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