generate_hyper3d_model_via_images

WHAT IT DOES

What generate_hyper3d_model_via_images does on Blender

AI agents invoke generate_hyper3d_model_via_images 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.

WHY IT NEEDS A POLICY

Why generate_hyper3d_model_via_images needs a policy

Based on the tool name and server context, this tool likely generates a 3D model from input images using the Hyper3D service, which involves triggering an external API/operation. The sibling tools 'generate_hyper3d_model_via_text' and 'get_hyper3d_status' suggest an async generation workflow. This is an Execute-class operation (triggers external computation). Confidence is lowered due to empty description.

From the tool's definition Tool name: generate_hyper3d_model_via_images — description is empty/uninformative

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_hyper3d_model_via_images Rate-limited

generate_hyper3d_model_via_images 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_hyper3d_model_via_images": {
      "limits": [
        {
          "counter": "generate_hyper3d_model_via_images_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 Blender, so you can run agents against it safely.

FAQ

Questions about generate_hyper3d_model_via_images

What does the generate_hyper3d_model_via_images tool do? +

generate_hyper3d_model_via_images. 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 generate_hyper3d_model_via_images? +

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

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

Can I rate-limit generate_hyper3d_model_via_images? +

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

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

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