AI agents use import_generated_asset_hunyuan to create or update resources in Blender — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender environment.
This tool imports/adds generated 3D assets into a Blender scene, which modifies the scene state by creating new objects or data. This is a reversible write operation (the imported asset can be deleted or the scene reverted). It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description states 'Import the asset generated by Hunyuan3D after the generation task is completed.' The action of importing an asset into Blender creates or adds new data to the scene.
Attacks that exploit this kind of access
Import the asset generated by Hunyuan3D after the generation task is completed. It is categorised as a Write tool in the Blender MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender MCP server in PolicyLayer and add a rule for import_generated_asset_hunyuan: 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.
import_generated_asset_hunyuan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the import_generated_asset_hunyuan 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 import_generated_asset_hunyuan. 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.
import_generated_asset_hunyuan 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.
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 →