Create a 3D model generation job using Hyper3D Rodin
AI agents invoke create_rodin_job 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.
This tool triggers an external operation — submitting a job to the Hyper3D Rodin service to generate a 3D model. It initiates a remote computational process whose effects depend on the arguments provided. It goes beyond a simple write (data creation) because it dispatches work to an external AI/3D generation service, analogous to executing a script or triggering an external operation.
From the tool's definition Create a 3D model generation job using Hyper3D Rodin
Attacks that exploit this kind of access
Create a 3D model generation job using Hyper3D Rodin. 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.
Register the MCP-Blender MCP server in PolicyLayer and add a rule for create_rodin_job: 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.
create_rodin_job 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 create_rodin_job 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 create_rodin_job. 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.
create_rodin_job 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.
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 →