import_generated_asset
AI agents use import_generated_asset to create or update resources in BlenderMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BlenderMCP environment.
This tool creates or modifies scene state by importing externally-generated 3D assets into Blender. While the description is empty (lowering confidence slightly), the name and context of sibling generation tools strongly indicate Write-category functionality. It does not delete data (not Destructive), does not execute arbitrary user code (not Execute), and does not involve financial transactions (not Financial).
From the tool's definition Tool name 'import_generated_asset' indicates asset import/integration into Blender. Sibling tools include 'generate_hyper3d_model_via_images' and 'generate_hyper3d_model_via_text', suggesting this tool integrates outputs from external AI model generation…
Attacks that exploit this kind of access
import_generated_asset. It is categorised as a Write tool in the BlenderMCP 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: 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.
import_generated_asset 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 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. 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 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 →