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.
The tool performs Write-category operations: it imports (adds/creates references to) generated or downloaded assets into the Blender scene, modifying the project state. This is reversible (assets can be deleted). No description provided, which lowers confidence slightly. It does not execute arbitrary code (that is execute_blender_code's role), delete data, or move money.
From the tool's definition Tool name 'import_generated_asset' indicates creation/addition of assets into a Blender scene. Context shows integration with asset generation tools (generate_hyper3d_model_via_images, generate_hyper3d_model_via_text, download_polyhaven_asset,…
Documented attack patterns abuse exactly the kind of access import_generated_asset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BlenderMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for import_generated_asset:
{
"version": "1",
"default": "deny",
"tools": {
"import_generated_asset": {
"limits": [
{
"counter": "import_generated_asset_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_generated_asset stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 (nanashi1526/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BlenderMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 BlenderMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.