generate_hyper3d_model_via_images
AI agents invoke generate_hyper3d_model_via_images to trigger actions in BlenderMCP. 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.
Based on the sibling tool 'generate_hyper3d_model_via_text' and server description mentioning Hyper3D Rodin for AI-generated 3D models, this tool likely triggers an external AI service to generate 3D models from images. This constitutes executing an external operation. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'generate_hyper3d_model_via_images' and server context describing AI-generated 3D models through Hyper3D Rodin; description is empty.
Attacks that exploit this kind of access
generate_hyper3d_model_via_images. It is categorised as a Execute tool in the BlenderMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
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 BlenderMCP. Nothing to install.
generate_hyper3d_model_via_images is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
generate_hyper3d_model_via_images is provided by the Blender MCP server (wenyen-hsu/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →